chore: Dispatch promotions repo instead of GitLab

[luqmanbello]

What it solves

Production deploys for the legacy Safe Apps still POST a GitLab pipeline-trigger webhook (gitlab.5afe.dev) that a deployer then plays manually, using static AWS keys stored as GitLab CI variables.

How this PR fixes it

The release flow now dispatches the gated react-apps-production.yml workflow in safe-global/safe-production-promotions via the safe-promotions-dispatcher GitHub App, the same swap safe-dashboard and the status page made. deployment.yml mints a short-lived App token, the release action passes it to prepare_production_deployment.sh, and the script runs gh workflow run with app + tag instead of the GitLab curl. tx-builder is skipped explicitly (it deploys via safe-tx-builder-tf since March). A failed dispatch logs an error annotation without breaking the nx chain, so last-release tagging still completes; the promotion can then be dispatched manually. The unused react-app-rpc-token action input is removed.

How to test it

Next workflow_dispatch release from main: affected apps upload to staging as before, and a pending run appears in safe-production-promotions per app instead of a GitLab pipeline. The GitLab path stays as fallback until one release passes through.

Screenshots

n/a

[datadog-official]

⚠️ Warnings

🚦 3 Pipeline jobs failed

CLA Assistant | CLAAssistant     

Deploy Apps | Pull Request     

Safe Apps E2E | Execute E2E tests     

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: dc4d2f5 | Docs | Give us feedback!}