fix: bundle explore link path

[vasco-santos]

After looking at the info in #279 and trying it out, I am a bit clueless if this is a good fix as this goes really outside my expertise. Sharing what I discovered.

Going to https://explore.ipld.io/#/explore/QmWYmE8fzNRYg48E5PaDhMfHqfbPjyQVmUjGQfgAsa4NYq and then opening its first link, it will work (https://explore.ipld.io/#/explore/QmWYmE8fzNRYg48E5PaDhMfHqfbPjyQVmUjGQfgAsa4NYq/Links/0), however opening the following link will fail (https://explore.ipld.io/#/explore/QmWYmE8fzNRYg48E5PaDhMfHqfbPjyQVmUjGQfgAsa4NYq/Links/0/Links/0). Per @rvagg input, I figured out the url should have the /Hash in, and trying it out worked: https://explore.ipld.io/#/explore/QmWYmE8fzNRYg48E5PaDhMfHqfbPjyQVmUjGQfgAsa4NYq/Links/0/Hash/Links/0

So, I discovered how to add the Hash, assuming it should always happen when we are on a path with multiple Links? Other solution is to inject the Hash on the table itself (I think by simply changing this https://github.com/ipfs/ipld-explorer-components/blob/master/src/lib/resolve-ipld-path.js#L48 to linkPath). Let me know if any of these solutions and my assumptions are correct

---

Note: The current error is like #284

Closes #279

[lidel]

Thank you for looking into this.

Unfortunately, this approach does not seem to work with go-ipfs, which is a hard blocker (ipfs-webui consumes go-ipfs API via js-ipfs-http-client).

I tested this in ipfs-webui and adding /Hash moves the problem one level deeper:
Opening QmWYmE8fzNRYg48E5PaDhMfHqfbPjyQVmUjGQfgAsa4NYq/Links/0/Hash/Links/0 and clicking on Links/0 opens a different CID than expected.

Seems that at some point the target gets confused with the root of the path.

Not sure if there is an easy fix that does not involve big refactor, see my comment #279 (comment), but injecting the hash on the table and limiting that behavior to dag-pb code path sounds like a safer approach.

[lidel]

Closing for now, let's continue in #279