fix(network-proxy): add unix socket allow-all and update seatbelt rules

[viyatb-oai]

Summary

Adds support for a Unix socket escape hatch so we can bypass socket allowlisting when explicitly enabled.

Description

• added a new flag, network.dangerously_allow_all_unix_sockets as an explicit escape hatch
• In codex-network-proxy, enabling that flag now allows any absolute Unix socket path from x-unix-socket instead of requiring each path to be explicitly allowlisted. Relative paths are still rejected.
• updated the macOS seatbelt path in core so it enforces the same Unix socket behavior:
  • allowlisted sockets generate explicit network* subpath rules
  • allow-all generates a broad network* (subpath "/") rule

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c17717fc37

ℹ️ 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]

Disallow unix-socket override when managed flag is omitted

Treating constraints.dangerously_allow_all_unix_sockets == None as allowed means existing managed configs that only constrain network.allow_unix_sockets can now be bypassed by setting network.dangerously_allow_all_unix_sockets = true. In that case validation passes here, and is_unix_socket_allowed then returns true for any absolute path, so the managed allowlist is effectively unenforced unless every policy is updated to add the new field explicitly.

Useful? React with 👍 / 👎.