refactor: IPFS_GATEWAY

[whizzzkid]

Original PR: #93

In this PR:

• fix / update npm test
• TBD - maybe we should only support gateways?
• confirm it works with ipfs.block.get from Kubo
• confirm it works with ipfs.block.get from JS-IPFS
• https://github.com/ipfs/public-gateway-checker (refactor to use gateway)
• solve issue with ip dependency requiring native node module (check this PR: fix: flag column and new ipfs-geoip dataset ipfs/public-gateway-checker#319)

Remaining

• update source dataset and regenerate b-tree, so users not only get storage savings thanks to DAG-CBOR, but also get updated GeoIP database
• cleanup add retry if gateway timeouts
• confirm it works with https://github.com/ipfs/ipfs-webui (refactor to use availableGatewayUrl and pass it similar to how we do it on explore page)

[lidel]

Thank you for snoke-testing!

I've restored ability to run things against local node by following convention from ipfs/specs#280 (IPFS_GATEWAY env).

Merging, let's continue in #93

[SgtPooki]

• update source dataset and regenerate b-tree, so users not only get storage savings thanks to DAG-CBOR, but also get updated GeoIP database
• cleanup add retry if gateway timeouts
• confirm it works with https://github.com/ipfs/ipfs-webui (refactor to use availableGatewayUrl and pass it similar to how we do it on explore page)

@whizzzkid are these being tracked anywhere else?