chore: use org-level TG_TOKEN secret

[Pigbibi]

改动

1 行：secrets.STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN → secrets.TG_TOKEN

环境变量名 STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN 不变，Cloud Run 运行时不受影响。

前置条件

• Org secret TG_TOKEN 已创建

🤖 Generated with Claude Code

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 293170ab9f

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

Update the workflow test for TG_TOKEN

This change makes every PR/main-push CI run fail: .github/workflows/ci.yml runs uv run --no-sync python -m pytest -q, and tests/test_sync_cloud_run_env_workflow.py:118 still asserts that this env entry uses ${{ secrets.STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN }}. I verified python -m pytest tests/test_sync_cloud_run_env_workflow.py -q fails on this assertion after the secret rename, so the test needs to be updated alongside the workflow change.

Useful? React with 👍 / 👎.