Don't assume an orchestrator port number, but pull it from nomad

[djeebus]

This keeps support for assuming an orchestrator port number, but only as a fallback. This allows us to place orchestrators where ever we want, with whatever port number we want, and the API will find them.

---

Note

API now discovers orchestrator IP/port from Nomad allocation resources (label grpc), with a configurable default fallback; Nomad job defines labeled ports and env wired from Nomad.

• Orchestrator discovery (API):
  • Switch from listing Nomad nodes to listing allocations with filter ClientStatus == "running" and JobID contains "orchestrator-".
  • Add health gating via isHealthy and resolve address by scanning AllocatedResources for port label o.portLabel (fallback to o.defaultPort).
  • Build NomadServiceDiscovery from allocation IP/port; logs when missing/found.
  • Add tests for isHealthy and port resolution across reserved/dynamic/shared networks in client_test.go.
• Configuration:
  • Introduce Config.DefaultOrchestratorPort (deprecated fallback) and Config.OrchestratorPortLabel (default grpc).
  • Thread defaultPort and portLabel into Orchestrator.
• Nomad job (iac/provider-gcp/nomad/jobs/orchestrator.hcl):
  • Define network { mode = "host" } with labeled ports grpc and proxy; services reference labels.
  • Set GRPC_PORT/PROXY_PORT from $${NOMAD_PORT_grpc}/$${NOMAD_PORT_proxy}.
• Cleanup:
  • Remove OrchestratorPort from packages/shared/pkg/consts/sandboxes.go.

^{Written by Cursor Bugbot for commit bd75947. This will update automatically on new commits. Configure here.}