[MS-1505] Add release dashboard promotion workflows

[meladRaouf]

JIRA ticket
Will be released in: no app release

Notable changes

• Add update-release-stage.yml — manual workflow_dispatch workflow to promote a version to production_ready (Beta), delivery_testing, or production. Looks up the GitHub Release for that version to find the APK download URL automatically. The version input is a choice dropdown seeded with the 15 most recent published release tags (wrapped in marker comments for automated regeneration), and stage is a choice of the three supported environments.
• Add reusable-update-dashboard.yml — reusable workflow that writes the promoted environment/version/apk_url/release_url into status.json on the gh-pages branch and commits/pushes the change, so the release status dashboard stays up to date.
• Add sync-release-stage-versions.yml — workflow triggered on release: published (and manual dispatch) that regenerates the version dropdown in update-release-stage.yml from the live list of release tags and commits the change back to main, keeping the dropdown in sync without manual edits.
• All workflow_dispatch inputs are passed via env: rather than interpolated directly into run: blocks, to avoid script injection.

Testing guidance

• Run update-release-stage.yml manually via workflow_dispatch, selecting a stage and version, and confirm status.json on gh-pages is updated with the correct version/apk_url/release_url and the dashboard reflects the change.
• Publish a release and confirm sync-release-stage-versions.yml runs and updates the version dropdown options in update-release-stage.yml on main.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[Copilot]

Pull request overview

Adds GitHub Actions workflows to manually promote a released app version to a given “stage” and keep a gh-pages-hosted release dashboard (status.json) updated, plus an automation to keep the manual workflow’s version dropdown in sync with published GitHub Releases.

Changes:

• Introduces a manual workflow_dispatch workflow to promote a version to production_ready, delivery_testing, or production, resolving the Release + APK URL via gh.
• Adds a reusable workflow that writes the promoted stage/version/urls into status.json on gh-pages and commits/pushes.
• Adds a workflow triggered on release: published (and manually) to regenerate the version choice list in the promotion workflow.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
.github/workflows/update-release-stage.yml	Manual promotion entrypoint; resolves release info and calls the reusable dashboard updater.
.github/workflows/reusable-update-dashboard.yml	Reusable workflow that updates status.json on gh-pages and pushes the change.
.github/workflows/sync-release-stage-versions.yml	Regenerates the promotion workflow’s version dropdown from published release tags and pushes updates to the default branch.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud