CLOUDP-361630 - release workflow that automatically creates git tag and Release Notes

[MaciejKaras]

Summary

This change intends to automate starting of MCK release. The workflow is started manually either from GitHub UI or cmd line, example:

 gh workflow run "Release MCK version"  -f version="1.6.1" -f commit_sha="27666bad626f042577e0ac609454b69dfb2ebfc8"

The process has three steps:

1. Create draft release with Release Notes - Start of the release workflow. This will create draft GitHub Release with generated Release Notes. Verify the release notes and proceed to next step. There could be other verifications added in the future.
2. Create Git Tag + start Evergreen jobs - manual approval will create a git tag on behalf of GitHub Actions bot. The tag will trigger evergreen release jobs as usual
3. Publish Release - this should be approved manually when all the evergreen jobs finished successfully. It will publish the GitHub Release and make it latest

Proof of Work

Started the workflow with command:

 gh workflow run "Release MCK version" --ref "maciejk/ar-initial-promotion" -f version="1.6.1-mk" -f commit_sha="27666bad626f042577e0ac609454b69dfb2ebfc8"

First step:

... and draft GH release (without a tag):

Creating Git tag:

... and draft GH release (with a tag):

Publish release:

... and public, latest GH release:

All of the above images are produced by this test.

Post steps

• After merging update the Release Guide accordingly

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you added changelog file?
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.6.1 Release Notes

[mircea-cosbuc]

LGTM!