fix: follow verified-fetch redirects when subdomains are disabled

[achingbrain]

Pass redirect: 'follow' to @helia/verified-fetch when subdomain support is enabled, otherwise we send a 301 with no Location header.

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works

[achingbrain]

I'm not sure how to write a test for this because the e2e tests only have a single server config.

@SgtPooki presumably this will be covered by the conformance tests after #67?

[SgtPooki]

presumably this will be covered by the conformance tests after #67?

Yea it should be covered by subdomain gateway conformance, though I don't think we will run gateway conformance against subdomains=disabled versions of this gateway?

[achingbrain]

That's interesting, we have to turn off subdomains to get tiros to work (from what I can see), because the flow goes like:

0. HTTP Gateway runs in a container with the name "ipfs"
1. Browser requests http://ipfs/ipns/filecoin.io
2. Browser is redirected to http://filecoin.io.ipns.ipfs
3. Browser fails with net::ERR_NAME_NOT_RESOLVED

This is because Docker doesn't support wildcards in container aliases so can't resolve filecoin.io.ipns.ipfs 🙄

I'm guessing Kubo has subdomains off by default and we have it on (which is better) so Kubo doesn't need any extra config.