Add support for BNSv2

[314159265359879]

Prior discussion: https://trustmachines.slack.com/archives/C05T570TNQJ/p1726223496583099?thread_ts=1725474426.269799&cid=C05T570TNQJ

I see gamma has adopted showing a "V1 (legacy)" and "V2" label. I'd prefer to show BNSv2 without a label and BNS V1 with "V1 deprecated" label, what do you think?

There was an issue with the first airdrop (expiration times were not right) and the airdrop process has restarted.

Here is the (updated BNSv2 v2) contract: P2QEZ06AGJ3RKJPBV14SY1V5BBFNAW33D96YPGZF.BNS-V2
https://explorer.hiro.so/txid/SP2QEZ06AGJ3RKJPBV14SY1V5BBFNAW33D96YPGZF.BNS-V2?chain=mainnet

We are waiting for Hiro to finalise work on the BNS API/docs. Then, we should be able to adopt it (they promised to make it as easy as possible for wallet providers).

The logo for BNSv2 has been changed slightly, new logo:

https://images.gamma.io/ipfs/QmUDBKgiCDW8J8db3bFBhnnVLHwguspGQLZ3zZ6t76ne45

[314159265359879]

By the way airdrop of names to V1 owners is still ongoing. about 1/7th to go I think.

[314159265359879]

I updated the first post with the BNSv2 contract. Airdrop was well on its way but there was an issue so it was redeployed and the airdrop is being replayed. You can read more about the details in this forum post: https://forum.stacks.org/t/megathread-bns-upgrade-discussion/14899/71

It is expected to take about 1 week to complete.

[markmhendrickson]

Note we have a project for these enhancements generally here. Let's capture distinct issues for that project in this related milestone instead of lumping into one issue.