feat: add support for resolving .eth domains

[akhileshthite]

Proposal:

All ENS-hosted content is typically stored on IPFS, with the .eth domain resolving to an IPFS content hash. Enhance the js-ipfs-fetch library to include support for resolving .eth domains into IPFS CIDs or IPNS paths. This feature could leverage ENS resolution libraries (e.g., ethers, @ensdomains/content-hash) to fetch the content hash of .eth domains.

Expected Workflow:

• A user calls the fetch function with a .eth domain, e.g., await fetch('vitalik.eth').
• The .eth domain is resolved to its associated content hash via ENS.
• The content hash is used to fetch the corresponding data from IPFS or IPNS.
• The resolved content is returned as the response.

Public RPC nodes:
https://chainlist.org/chain/1

[akhileshthite]

p2plabsxyz/peersky-browser#7