CLDSRV-859: trigger scality-kms release workflow on cloudserver release

[tcarmet]

Summary

• Add a new job to the release workflow that automatically triggers the scality-kms release workflow after a successful cloudserver release
• Use GitHub App authentication to trigger the cross-repository workflow
• Add repository owner check to prevent forks from attempting to trigger the workflow

This ensures the KMS server image is built with the latest cloudserver base image whenever a new cloudserver release is published.

Related to scality/scality-kms#79

[bert-e]

Hello tcarmet,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Incorrect fix version

The Fix Version/s in issue CLDSRV-859 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 9.2.29

• 9.3.5

• 9.4.0

Please check the Fix Version/s of CLDSRV-859, or the target
branch of this pull request.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.15%. Comparing base (9b836b8) to head (172ab3c).
✅ All tests successful. No failed tests found.

Additional details and impacted files

see 2 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.2    #6089      +/-   ##
===================================================
- Coverage            84.17%   84.15%   -0.03%     
===================================================
  Files                  204      204              
  Lines                13124    13124              
===================================================
- Hits                 11047    11044       -3     
- Misses                2077     2080       +3     

Flag	Coverage Δ
file-ft-tests	67.62% <ø> (ø)
kmip-ft-tests	28.19% <ø> (ø)
mongo-v0-ft-tests	68.84% <ø> (-0.03%)	⬇️
mongo-v1-ft-tests	68.85% <ø> (ø)
multiple-backend	35.24% <ø> (ø)
sur-tests	35.75% <ø> (ø)
sur-tests-inflights	37.60% <ø> (ø)
unit	69.71% <ø> (ø)
utapi-v2-tests	34.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.