Hyperloop Gin server and logs forwarding

[sitole]

• Initial setup for hyperloop server (gin, generated openapi schema, request validation...)
• Logs endpoint that received logs from sandbox and forwards them to Vector logs collector
• Removed need for LOGS_COLLECTOR_PUBLIC_IP in orchestrator, replaced with hyperloop

[sitole]

task for future IaC removal https://linear.app/e2b/issue/ENG-3029/remove-vector-public-load-balancer-from-iac

[sitole]

Bug: Hyperloop Server Shutdown Context Issue

The hyperloop server's shutdown uses the main application context (ctx) instead of closeCtx. This is inconsistent with other services and means the server won't respect shutdown timeouts or immediate cancellation during forced stops, potentially causing it to hang or fail prematurely.

packages/orchestrator/main.go#L529-L534

Thank you, good bot!

[sitole]

cca1c51 fixes the issue introduced at #1105 that caused all sandbox logs coming from new envd builds to never show to customers, as the teamID we are using for log filtration was removed.

[jakubno]

can you move it under /logs?

[sitole]

Then we need to send it somehow to envd. Now we are using address parameter in the init request, and with adding back compatibility, we would need to send /logs here too, to make it not re-usable for different things.

Maybe we can do /logs, update in newer envds and do / just for back compatibility in http server?

[sitole]

dd5cede is just wip for now. Moves url for sandbox logs to /logs/push with back compatibility for older envd. Re-do of metadata sync in envd.

[sitole]

This can be closed after https://linear.app/e2b/issue/ENG-2460/replace-vector-public-ipv4-address-with-orchestrator-http-server