[feature] Manage redirectors from tavern

[hulto]

Is your feature request related to a problem? Please describe.

• Sometimes we want to disable a redirector if an agents been caught.
• Centralizing this in Tavern server streamlines experience

Describe the solution you'd like

• New ent for redirector: IP that the server sees, transport type, supported activities, active or not
• Redirectors register with the server (some kinda auth probably MTLS or gcp OIDC)
• New endpoint to manage services (probably gonna be used by the builder as well)
• Edge from agent to redirector
• Expose redirector and transport in detail views and filters (often want to filter by beacons that support high bandwidth esp for things like rev shell)
• Allow modification of redirector via services API (disable / enable) - When disabled redirectors should still respond to traffic with opsec things (look like a real website but not c2 comms)

Describe alternatives you've considered
Na

Additional context
Na

[egypt]

It sounds like you are envisioning standalone programs for each transport protocol that translate agent messages from whatever they speak to the Tavern grpc protocol. Is that the idea for this Issue?

[hulto]

It sounds like you are envisioning standalone programs for each transport protocol that translate agent messages from whatever they speak to the Tavern grpc protocol. Is that the idea for this Issue?

That part is actually already done in #1008 and #988.

This issue is to centralize redirector configuration in the backend. Which will require redirectors authenticate to the backend and then add an ent that represents each redirector and its current configuration.

The new ent can be added following these docs(https://docs.realm.pub/dev-guide/tavern#creating-a-new-model) tho the Auth component is more ambiguous ideally we continue to use OIDC tho it's unclear if we mint a one off token or create a GCP service account.