[CLIENT-3467] CI/CD: use orchestrator workflow instead of individual shared workflows

[juliannguyen4]

No description provided.

In general, the fix is to add an explicit permissions block either at the workflow root or on the specific job so that GITHUB_TOKEN does not default to potentially broad repository/organization permissions. The permissions should be limited to the least privilege necessary for this workflow.

For this specific workflow, the job only sets up the JFrog CLI with OIDC and runs jf rbp .... There is no evidence of creating or modifying issues, pull requests, releases, or repository contents via the GitHub API. The safest change that preserves existing behavior is to add a job-level permissions block that restricts contents to read. If in reality the job does not need GITHUB_TOKEN at all, you could go further and use permissions: {}; however, that may cause future steps added to this reusable workflow to fail unexpectedly. A conservative, compatible fix is therefore:

permissions:
  contents: read

placed under the promote-release-bundle-to-dev job, aligned with other job keys like runs-on. No imports or additional methods are needed because this is a GitHub Actions YAML configuration change only.

Concretely, in .github/workflows/promote-release-bundle.yml, update the promote-release-bundle-to-dev job definition (around line 21–24) to insert a permissions block between runs-on: ubuntu-24.04 and env:.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.48%. Comparing base (88dadfa) to head (a2abc21).
⚠️ Report is 3 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #994   +/-   ##
=======================================
  Coverage   83.48%   83.48%           
=======================================
  Files          99       99           
  Lines       14402    14402           
=======================================
  Hits        12024    12024           
  Misses       2378     2378           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.