fix(ci): enable api-proxy for codex workflow

[Mossaka]

Tracking issue from closed PR #828.

Codex was failing with error sending request for url (http://172.30.0.30:10000/responses) because the workflow configured base URLs pointing to api-proxy but never started the container.

Changes needed

• Add --enable-api-proxy flag to awf command in Run Codex step
• Remove manual OPENAI_BASE_URL/ANTHROPIC_BASE_URL env vars (AWF sets these automatically)
• Add OPENAI_API_KEY to env block (required for api-proxy auto-detection)
• Remove 172.30.0.30 from allowed domains list (internal routing)

Original PR: #828

[github-actions]

👋 Hello! I noticed this issue is closely related to other open issues that are part of the same api-proxy configuration work:

• fix(squid): add api-proxy support (ports 10000/10001, IP 172.30.0.30) #833 - "fix(squid): add api-proxy support (ports 10000/10001, IP 172.30.0.30)" - Deals with Squid proxy configuration to allow traffic to api-proxy service
• fix: use dst ACL for IP addresses in squid config #835 - "fix: use dst ACL for IP addresses in squid config" - Fixes Squid ACL type mismatch for IP addresses vs. domain names

These three issues form a related set:

• fix(squid): add api-proxy support (ports 10000/10001, IP 172.30.0.30) #833 adds the underlying Squid configuration support for api-proxy
• fix: use dst ACL for IP addresses in squid config #835 fixes the Squid ACL type handling for IP addresses (172.30.0.30)
• fix(ci): enable api-proxy for codex workflow #834 (this issue) enables api-proxy in the codex workflow that depends on those fixes

All three reference the same error pattern (`error sending request for url ((172.30.0.../redacted) and were created from closed PRs as tracking issues. They appear to be sequential dependencies rather than duplicates - each addresses a different layer of the api-proxy integration.

This is an automated message from the issue duplication detector.

AI generated by Issue Duplication Detector

[Mossaka]

Closing as this appears to have been resolved in main. The smoke-codex.lock.yml workflow now includes the --enable-api-proxy flag in the awf invocation, resolving the codex failure with 'error sending request for url (http://172.30.0.30:10000/responses)'.