feat: use worker bindings interacting from api to gateway

[vasco-santos]

This PR adds:

• worker bindings from API to Gateway

Implementation details:

• miniflare support for testing bindings is still quite limited, we cannot spin up the other worker build, and it does not seem to support ESM either...
• bindings from API to Gateway tests use custom script that does the fetch to the local daemon converting subdomain resolution to path resolution. This is because we can't resolve localhost subdomains locally unless we add them to /etc/hosts, which is not cool, given we can't use tools like https://github.com/feross/hostile without sudo for pre and post tests... There was the option of relying on services like https://readme.localtest.me/ but don't really want to use external services in CI

Needs:

• [x] wrangler 2

Initial binding part of https://github.com/nftstorage/nftstorage.link/issues/101 to move to worker bindings setup

[cloudflare-pages[bot]]

Deploying with    Cloudflare Pages

Latest commit:	762c382
Status:	✅  Deploy successful!
Preview URL:	https://f457bde5.nftstorage-link.pages.dev
Branch Preview URL:	https://fix-use-worker-bindings.nftstorage-link.pages.dev

View logs

[vasco-santos]

Will it really get us a common cache? Or do we need to test it to find out?

Let's talk sync on this. btw, this is not related at all with this PR 😛 This is basically using bindings between nftstorage.link gateway and API (for perma-cache) as part of https://github.com/nftstorage/nftstorage.link/issues/101