Create infrastructure for testing and validating retrieval reliability with Helia

[SgtPooki]

discussed in https://pl-strflt.notion.site/Reliable-retrieval-monitoring-project-plan-formation-ce2190c2ad054a44b8d0fca7d2cf6006?pvs=4

### Tasks
- [x] Phase 0: validate with probelab that they can pull from GitHubContainerRegistry
- [x] Phase 1: create helia nodejs gateway that can work with probelab's tiros
- [x] Phase 1: implement /api/v0/repo/gc to run garbage collection upon request
- [x] Phase 1: respond to `<host>/<namespace>/request` using a simple server
- [x] Phase 1: Tiros support for a Helia gateway: https://github.com/plprobelab/tiros/pull/5
- [x] Phase 1: problab.io testing website using a Helia gateway: https://github.com/plprobelab/probelab-infra/pull/75
- [x] Phase 1: Investigate helia-http-gateway crashing issue. - https://github.com/ipfs/helia-http-gateway/issues/18
- [ ] https://github.com/ipfs/helia-http-gateway/issues/12
- [x] Ensure helia maintainers have access to a graph showing successful helia-http-gateway runs
- [x] Decide on how we want to handle running & displaying 3 separate helia-http-gateway setups with tiros
- [x] Get https://github.com/ipfs/helia-ipns/pull/55 merged and pulled into this repo so we can improve ipns queries.
- [x] Document the Helia configurations run on probelab.io: https://github.com/plprobelab/website/pull/85
- [x] migrate to @helia/verified-fetch -> https://github.com/ipfs/helia-http-gateway/pull/63