[BRE-1935] Migrate workflow: github-release.yml

[AmyLGalles]

Summary

This PR completes the finalize-source stage of migrating github-release.yml to bitwarden/deploy.

The workflow has been replaced with a trigger-actions caller that forwards to release-ios.yml in bitwarden/deploy. This preserves the same developer interface while centralizing release orchestration.

Changes

• Replace github-release.yml implementation with trigger-actions caller
• Preserves workflow_dispatch trigger with same inputs (artifact-run-id, release-ticket-id)
• Forwards inputs via data payload to release-ios.yml task in bitwarden/deploy

Developer Impact

Developers can continue to trigger releases the same way:

gh workflow run github-release.yml --repo bitwarden/ios \
  -f artifact-run-id=<run-id> \
  -f release-ticket-id=<ticket-id>

The workflow now routes through bitwarden/deploy's release-ios.yml for execution.

Related

• draft PR: The migrated workflow in bitwarden/deploy (release-ios.yml) is already merged to main
• Next step: After this merges, run /migrate-workflow-full ios github-release.yml wire-trigger to add the receiver job to trigger-actions.yml

Testing

After merge, test with:

gh workflow run github-release.yml --repo bitwarden/ios \
  -f artifact-run-id=<valid-run-id> \
  -f release-ticket-id=RELEASE-XXXX

Verify that it triggers release-ios.yml in bitwarden/deploy successfully.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.98%. Comparing base (e9514dc) to head (8803215).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2874      +/-   ##
==========================================
- Coverage   81.24%   78.98%   -2.27%     
==========================================
  Files        1028     1151     +123     
  Lines       66164    73459    +7295     
==========================================
+ Hits        53756    58022    +4266     
- Misses      12408    15437    +3029     

☔ View full report in Codecov by Harness.
📢 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.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed the migration of .github/workflows/github-release.yml from an in-repo release implementation to a bitwarden/deploy trigger-actions caller. The change preserves the workflow_dispatch interface (artifact-run-id, release-ticket-id) and forwards inputs to the release-ios task. Verified that the removed scripts (download-artifacts.sh, jira-get-release-notes, log-inputs) remain referenced by other workflows and are not orphaned, and that the new top-level permissions: {} with a scoped deployments: write job permission tightens the workflow's token scope. No security, correctness, or breaking-change findings met the confidence bar for inline comments.

Code Review Details

No blocking findings.

Notes for the author (non-blocking, no action required):

• The branch: ${{ github.ref_name }} input replaces the original logic that derived the release branch from the artifact run's headBranch (including the main/release/* protection check). This behavior now depends on the receiving release-ios.yml in bitwarden/deploy; worth confirming the receiver enforces the equivalent branch validation.
• The hold label is present, consistent with the PR description noting the receiver job must be wired in trigger-actions.yml before this can merge.