feat: Handle special resolvers in CI

[SgtPooki]

We need to update CI to check for stale gateways (there is an issue for this, but I don't have the link right now). We need to ensure that special gateways have the appropriate logic so that they're not considered obsolete when the CI workflow runs.

subtasks

• create special-gateways.json for gateways that require a special resolver logic

related

• feat: add public.records gateway #289 (comment)
• feat: add public.records gateway #289 (comment)
• Github actions should test new gateway PRs #248
• Abstract and encapsulate gateway checking logic from this package and JayBrown/Tools/tree/master/ipfg #192

[lidel]

Perhaps we should move these special gateways away from gateways.json into a special-gateways.json and include additional metadata about the type (Tor, Handshake, etc) with link to software that is required for use?

This way testing on CI will be easier: we will be able to test Handshake and Tor ones in separate jobs with different resolvers/setups etc.

[SgtPooki]

@lidel i like that idea. Should be easy to do while also helping call them out for those interested, instead of having to infer it from buried logic.