Release Label creation automation

[prudhvigodithi]

Is your feature request related to a problem? Please describe

Coming from the RFC (Improving public engagement for OpenSearch release process) label creation automation should help reduce some manual steps as part of the release preparation.

Describe the solution you'd like

Create the release label for each component repo as part of the version increment.
Having the label created as part of the version increment will ensure:

• The Labels are not created manually by an release manager or a repo owner
• The Labels are used for release issues/PR's
• The AUTOCUT automation can use the created labels created tag the AUTOCUT issues
  Sample failure

+ gh issue create --title '[AUTOCUT] OS Distribution Build Failed for asynchronous-search-2.9.0' --body '***Received Error***: **Error building asynchronous-search, retry with: ./build.sh manifests/2.9.0/opensearch-2.9.0.yml --component asynchronous-search**.
                      The distribution build for asynchronous-search has failed.
                      Please see build log at https://build.ci.opensearch.org/job/distribution-build-opensearch/8017/consoleFull' --label autocut,v2.9.0 --label untriaged --repo https://github.com/opensearch-project/asynchronous-search.git
could not add label: 'v2.9.0' not found

Describe alternatives you've considered

No response

Additional context

No response

[prudhvigodithi]

Release Labels are now auto created if does not exist and also added to version increment PR's.

OpenSearch Sample version increment PR with added v2.9.0 label:
opensearch-project/asynchronous-search#291

For OpenSearch Dashboards the label does exists before.

Label creation skipped as v3.0.0 already exists.

After the workflow execution https://github.com/opensearch-project/opensearch-build/actions/runs/5351069331/jobs/9704460699 labels are created.

[prudhvigodithi]

Closing this issue as the label creation is automated with the version increment workflows.

[prudhvigodithi]

With the PR #3703 merged, the workflows handles the core repos label creation while skipping them from actual version increment.