feat: support ipns/<name> & dnsLink resolution

[SgtPooki]

We should enable users to explore paths like:

• /ipns/docs.ipfs.tech
• /ipns/k51...
• foobar.host.com - with DNSLink TXT entry

---

When typing things like /ipns/k51..., /ipns/ipfs.io into the browse/inspect bar if you hit inspect it'll take you to the explore page and will error.

There are a variety of errors depending on the mutable identifier type:

• /ipns/k51... -> Error: No resolver found for codec "libp2p-key"
• /ipns/12D3... -> HTTPError: invalid path "12D3K...": selected encoding not supported
• /ipns/Qm... -> Seems to hang/break things (but could be mistaken)
• /ipns/ipfs.io -> Error: invalid character '.' in 'ipfs.io'

Related

• https://github.com/ipfs/ipfs-webui/issues/1884
• https://github.com/ipfs/ipfs-webui/issues/1076
• https://github.com/ipfs/ipfs-desktop/issues/2649

[SgtPooki]

After https://github.com/ipfs/ipld-explorer-components/pull/406, this work becomes trivial: just use https://github.com/ipfs/helia-ipns