Rename Google Voice config to recipients

[Pigbibi]

Summary

• rename Google Voice notification destination config from gateway to recipients
• document that recipients are email-form addresses: normal mailboxes receive email, Google Voice mailboxes/addresses can also trigger GV prompts
• update QPK and strategy dependency pins to the recipients config commits
• keep old GOOGLE_VOICE_TO and GOOGLE_VOICE_GATEWAY env names in Cloud Run cleanup lists

Tests

• PYTHONPATH=/home/ubuntu/Projects/QuantPlatformKit/src:/home/ubuntu/Projects/UsEquityStrategies/src:. .venv/bin/python -m pytest tests/test_runtime_config_support.py tests/test_rebalance_service.py tests/test_sync_cloud_run_env_workflow.py
• .venv/bin/python -m ruff check . (not run: Firstrade .venv has no ruff module)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1fed953405

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

Read legacy Google Voice env during migration

The runtime settings now read only CRISIS_ALERT_GOOGLE_VOICE_RECIPIENTS, so deployments that still have only the previous CRISIS_ALERT_GOOGLE_VOICE_GATEWAY variable (for example, environments where vars were not renamed yet or env-sync is disabled) will resolve an empty recipient list and stop sending Google Voice alerts after this release. Please keep a temporary fallback to the legacy env key while migrating existing environments.

Useful? React with 👍 / 👎.