Expose /routing/v1 HTTP APIs for proxying DHT+IPNI

[lidel]

part of #13

The idea behind someguy is to be a simple app that people can run to have delegated routing endpoint that performs DHT+IPNI lookups in parallel.

I believe our ecosystem still needs this: delegated DHT via a HTTP endpoint is something that will benefit JS implementations running in browser (cc @achingbrain @tinytb), mobile browsers and low-power IoT devices (cc @autonome).

Proposed next steps

Since Reframe was abandoned, someguy should be refactored to provide an endpoint compatible with GET /routing/v1/providers/{CID} from IPIP-337. This allows users to self-host and use it in their web apps.

TODO

TBD if we want to do this work without streaming support, or wait until we have it. Thoughts @aschmahmann ?

• (MVP) implement GET /routing/v1/providers/{CID} as-is?
• Create IPIP that extends API introduced in IPIP-337 to support streaming responses (so someguy can start responding with providers as it crawls the DHT, and does not block request for multiple seconds)
  • done: IPIP-410: Streaming Routing V1 HTTP API specs#410