feat(exec-server): add Noise rendezvous environment

[apanasenko-oai]

Why

Codex can run a remote exec server through the Noise relay, but the normal
environment-manager path could not establish an environment-registry-backed
harness connection. Signed rendezvous URLs and harness authorizations are
short-lived, so reconnects must fetch a fresh bundle instead of retaining
stale connection credentials. A stalled registry request must also fail within
the regular remote connection deadline, without exposing these credentials in
debug logs.

Issue: N/A (internal environment-service integration).

What Changed

• Add environment-manager configuration for a registry-backed Noise rendezvous
  environment.
• Request a fresh bundle from
  /cloud/environment/{environment_id}/connect for every physical harness
  connection, using the existing 10-second remote connection timeout.
• Share the Environment Registry register, connect, and validate wire payloads
  through codex-exec-server and codex-core-api.
• Redact the signed rendezvous URL and harness authorization from the public
  connect response's Debug output.
• Add focused coverage for registry bundle retrieval, stalled requests, and
  credential redaction.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 79d74a814e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a3cabe9360

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fa041fad2f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[apanasenko-oai]

[from Codex]: Addressed the registry-connect review feedback in aed3990: the public connect response now redacts signed credentials in Debug output, and /connect uses the existing 10-second remote connection timeout with stalled-response coverage. just test -p codex-exec-server passes (261 tests). CI is still running on this SHA.