IPNS and DNSLink fail to load in the explore tab

[aschmahmann]

Describe the bug
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.

This bug might be related to explore.ipld.io more than here, but since we depend on similar components I'm filing here. Feel free to move or redirect.

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'

To Reproduce
Steps to reproduce the behavior:

1. Go to Status Page
2. Click on Browse bar
3. Type in one of the paths above and click the Inspect button
4. See error

Expected behavior
IPNS resolution should work (i.e. resolve the IPNS path to the IPFS path and continue as normal). Alternatively some error like "IPNS not supported" would work and turn the rest of this into a feature request.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windowsd 10
• Browser: Chrome
• Version 96

[lidel]

This is a sensible enhancement.

• At the very minimum, anything other than CID or /ipfs/CID/... should get resolved to an immutable content path before being passed to IPLD Explorer component

Currently, it errors:

Note: /ipns/en.wikipedia-on-ipfs.org/wiki/ is a HAMT-sharded unixfs dir

If anyone wants to work on this, open PR in https://github.com/ipfs/ipld-explorer-components and ping @lidel for review/guidance.

[SgtPooki]

related: #1076

[SgtPooki]

closing in favor of ipfs/ipld-explorer-components#400