fix(release): add missing Intel V8 signing entitlement

[malsamiri-oai]

Why

Intel macOS release binaries crash on the first Code Mode tool call while V8 creates its code range. The x86_64 V8 allocator later makes a non-MAP_JIT reservation executable, which Hardened Runtime rejects when the signature contains only com.apple.security.cs.allow-jit.

Tracks SE-8006.
Fixes #28390.

What

• check in an entitlement profile for each macOS release binary
• grant allow-jit and allow-unsigned-executable-memory to codex, codex-app-server, and codex-code-mode-host
• keep codex-responses-api-proxy on its existing allow-jit-only profile
• resolve entitlement paths directly from the binary name during signing and final verification, failing if the profile is missing
• verify the expected Mach-O architecture and exact entitlement dictionary for the signed binary, tar.gz, zstd, package, and DMG copies

Verification

• just test-github-scripts (33 tests)
• UV_CACHE_DIR=/private/tmp/codex-uv-cache just fmt-check
• plutil -lint on all four entitlement profiles
• parsed rust-release.yml as YAML
• git diff --check
• ad-hoc Hardened Runtime signing smoke on an x86_64 Mach-O slice: strict codesign verification passed; the Codex profile contained both keys and the proxy profile retained only allow-jit

Release validation

Run a native Intel smoke of the final Developer ID-signed x86_64 Codex binary through V8 isolate creation before shipping. PR #30849 is diagnostic scaffolding, but its non-sandbox release job currently fails in the harness before V8 starts, so it is not counted as coverage here.

[Norcy]

Who can merge it? We need it

[anp-oai]

At a high level I think I'd prefer just having an entitlements file checked in for each binary instead of dynamically selecting them in a script. How hard would that be?

[malsamiri-oai]

@anp-oai Updated this to use checked-in entitlement files per binary and removed the selector script. codex, codex-app-server, and codex-code-mode-host now use the V8 entitlement profile, while the responses proxy keeps its existing allow-jit-only profile. Could you take another look when you have a chance?