[CLIENT-3467] CI/CD: Publish artifacts to JFrog using release bundles

[juliannguyen4]

No description provided.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.91%. Comparing base (f762c03) to head (cab272e).
⚠️ Report is 7 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #826      +/-   ##
==========================================
- Coverage   82.03%   81.91%   -0.12%     
==========================================
  Files          99       99              
  Lines       14724    14024     -700     
==========================================
- Hits        12079    11488     -591     
+ Misses       2645     2536     -109     

☔ 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.

To fix the problem, add a permissions key to the root level of the workflow file (.github/workflows/dev-workflow-p2.yml). This key should set the least necessary privileges required for the workflow to function. At a minimum, set contents: read, and add more granular permissions only if a job requires them (such as pull-requests: write if you manage PRs, or issues: write if you open/modify issues). Since most jobs reuse other workflows and interact mostly with artifacts, no write permissions are obviously required for contents, so start with just contents: read. If upon workflow usage additional permissions errors arise, add the minimum necessary permissions for each required type.

Edit .github/workflows/dev-workflow-p2.yml and insert a permissions block at the top level, directly after the name: field and before on:. For now, only set contents: read.

The best fix is to add an explicit permissions block as early as possible in the workflow YAML file, typically just below the name: and before the on: key (which will apply to all jobs that do not specify their own permissions block). The permissions block should specify only those privileges required by the workflow (preferably contents: read unless the jobs require additional write privileges, such as contents: write or issues: write). Since the workflow is handling artifact uploads, version bumps, and possibly PR-related changes, it's safe to start with contents: read and grant more if needed after a functional test. As required and as a minimal baseline, the recommended block is:

permissions:
  contents: read

You can later strengthen or refine this if the workflow needs more (such as pull-requests: write).

What to do:

• In .github/workflows/dev-workflow-p2.yml, insert a permissions: block after the name: field, before the on: block (after line 1).
• Use the recommended minimal setting: contents: read.

No imports or new methods are required for this change, as it is a configuration edit.

---