feat: add gateway config option for http and ws requests

[ao-anam]

Summary by cubic

Adds an optional proxy config to route REST and WebSocket signalling through a custom proxy, with validation and forwarding metadata.

• New Features
  • Proxy routing via new api.proxy (ProxyConfig) for API, engine REST, and WebSocket signalling; WebRTC media stays direct.
  • Validation: api/engine accept absolute URLs or paths starting with /; websocket must be ws:// or wss://.
  • Forwarding metadata: REST sends X-Forwarded-Host, X-Forwarded-Proto, X-Original-URI, X-Anam-Target-Url; WS adds x_forwarded_* and x_original_uri query params.
  • Clients updated to honor proxy: CoreApiRestClient, EngineApiRestClient, SignallingClient; validated and passed from AnamClient.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[cubic-dev-ai]

1 issue found across 13 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="src/modules/EngineApiRestClient.ts">

<violation number="1" location="src/modules/EngineApiRestClient.ts:25">
The proxy request logic is duplicated between `EngineApiRestClient` and `CoreApiRestClient`. This violates the DRY principle and should be extracted into a single, shared utility function to prevent inconsistencies and improve maintainability.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}