fix(codex): limit WebSocket connection churn

[ItsAlbertZhang]

Summary

• Prune the reusable Codex WebSocket pool to 40 least-recently-active idle connections when it grows beyond 50.
• Enforce at least one second between fresh WebSocket connection attempts.
• Retry an origin WebSocket upgrade 403 once after a three-second cooldown.
• Keep explicit proxy CONNECT rejections terminal and preserve existing retry and fallback behavior.

Implementation notes

• Track pool activity independently from the creation timestamp used for TTL expiry.
• Skip leased connections during cleanup and release socket guards before returning reusable connections to the pool.
• Keep origin-versus-proxy connection provenance private to the WebSocket connector.
• Apply the connection timeout separately to each network attempt.

Testing

• cargo test --lib providers::codex::websocket::tests:: — 37 passed
• cargo test --test codex_websocket_proxy — 1 passed
• cargo test --test codex_websocket — 9 passed
• cargo test --test smoke_cutover smoke_codex_websocket_stream_returns_delta_before_terminal -- --exact — passed
• cargo clippy --all-targets --all-features — passed with pre-existing warnings

Full cargo test reaches three pre-existing cursor_native mock-upstream HTTP 502 failures unrelated to this change.

Fixes #87

🤖 Generated with Claude Code

[raine]

Thanks for the thorough fix!