Automate manual steps while creating release candidate

[gaiksaya]

Is your feature request related to a problem? Please describe

We have automated most of the steps required to generate a release candidate. However, below steps are still manual:

1. Click docker build option to check build-with-tag in distribution build jobs on jenkins.
2. Post comment on release issue that new RC is ready for build. Per RC all that changes are the build numbers.
3. Number of the RC in the distribution build job
4. RC build does not validate the artifact at the end of the job. It should validate all artifacts it generated and only then declare it as a release candidate.
5. Should also post the docker scan details in the GH comment about RC

P1 items:

1. Should have the code coverage data for current release compared to last release (Not RC, last release) It is one of the entry criteria today but we do not have a mechanism to track it.

Acceptance criteria:

Automate the following manual actions

1. Automatically select build-with-tag for docker in distribution build jobs on jenkins.
2. Post comment on release issue that new RC is ready for build
3. Number of the RC in the distribution build job
4. Validate RC
5. Post the docker scan details in the GH comment about RC

Describe the solution you'd like

See above

Describe alternatives you've considered

No response

Additional context

No response

[gaiksaya]

@opensearch-project/engineering-effectiveness Please feel free to add any more ad-hoc steps that needs to be automated while creating RC.
Thanks!

[prudhvigodithi]

One more additional point.
To consider it a valid RC the build and validation should pass, later the parameter RC_NUMBER should be updated based on the results of the build and validation.