Address any remaining name resolution issues with BNS endpoints

[sabbyanandan]

As we continue to resolve one-off issues reported on BNS name resolution (see: #1159 / #1175), it'd be helpful to review all the BNS endpoints to make sure the BNS names are resolved correctly for all of them.

discussion point:
There are V1 and V2 endpoints, and a transaction that spawns either or both the endpoints require a different strategy for name resolution.

[rafaelcr]

Relevant issues:

• zonefiles do not track canonical chain state correctly #1273
• /v1/names/wowscience.id.stx is not returned by the API #1269
• BNS name renewal ->new expired_block value #1176
• Support subdomain update validation #1088
• Fix 500 error in /v1/names/:name #1064

[friedger]

This one as well: #1291

[blockstack-devops]

🎉 This issue has been resolved in version 5.0.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[blockstack-devops]

🎉 This issue has been resolved in version 5.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[blockstack-devops]

🎉 This issue has been resolved in version 7.0.0-stacks-2.1.2 🎉

The release is available on:

• npm package (@stacks-2.1 dist-tag)
• npm package (@stacks-2.1 dist-tag)
• GitHub release

Your semantic-release bot 📦🚀