Address any remaining name resolution issues with BNS endpoints

[sabbyanandan]

As we continue to resolve one-off issues reported on BNS name resolution (see: https://github.com/hirosystems/stacks-blockchain-api/pull/1159 / https://github.com/hirosystems/stacks-blockchain-api/pull/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:

• [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1273
• [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1269
• [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1176
• [ ] https://github.com/hirosystems/stacks-blockchain-api/issues/1088
• [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1064

[friedger]

This one as well: #1291

[blockstack-devops]

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

The release is available on:

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

Your semantic-release bot :package::rocket:

[blockstack-devops]

:tada: This issue has been resolved in version 5.0.0 :tada:

The release is available on:

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

Your semantic-release bot :package::rocket:

[blockstack-devops]

:tada: This issue has been resolved in version 7.0.0-stacks-2.1.2 :tada:

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 :package::rocket: