feat(ipns): records with V2-only signatures

[hacdias]

See ipfs/boxo#339.

• Note that this also removes the REFRAME routing support. It has been deprecated and the deprecated package has conflicts with the changes we made to boxo/ipns. It wouldn't make sense to update it since it's deprecated (HTTP Router only uses Addresses.Swarm #9823 (comment)).

[lidel]

Thanks! Lgtm, but needs tests, probably in test/sharness/t0100-name.sh (fine to add or migrate them to test/cli/harness if you dont want to write bash)

• ipfs name publish + resolve + inspect with and without v1compat

[lidel]

Some UX papercuts and missing tests need to be addressed (details below),
and needs to be rebased after ipfs/boxo#339 lands,
but otherwise lgtm.

@hacdias do you think we should include this in 0.21 (#9814), or do we do push both to 0.22? Since V2-only is opt-in, it should be safe to ship sooner, but ok to play it safe and push to 0.22

[hacdias]

@lidel I addressed the feedback and merged on Boxo side. I will be merging here once CI passes.

Regarding Kubo 0.21: I don’t mind either way. If we do an RC4 (let’s hope not), I will include it. Otherwise, let’s move it to Kubo 0.22. In case we don’t want to include it in Kubo 0.21 and there’s an RC4, I do not mind doing a cherry-picked release.

For now, I will assume 0.22 - if we end up doing RC4, I will update the changelog accordingly.