Updates backport workflow

[DarshitChanpura]

Description

Updates backport workflow to allow adding backport failure labels to failed auto-backports.

Category

Maintenance

Why these changes are required?

To allow easier tracking of failed backport PRs.

What is the old behavior before changes and new behavior after changes?

No tracking before this change.

Issues Resolved

• Resolves Add a backport-failed label to failed backports #2073

Check List

- [ ] New functionality includes testing
- [ ] New functionality has been documented

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.17%. Comparing base (0ed2cf2) to head (85dda20).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2074   +/-   ##
=======================================
  Coverage   71.17%   71.17%           
=======================================
  Files          96       96           
  Lines        2598     2598           
  Branches      387      387           
=======================================
  Hits         1849     1849           
  Misses        649      649           
  Partials      100      100           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security-dashboards-plugin/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/security-dashboards-plugin/backport-2.x
# Create a new branch
git switch --create backport/backport-2074-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 54955ff8c1f9b37afa2df60503d17bef5702282b
# Push it to GitHub
git push --set-upstream origin backport/backport-2074-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security-dashboards-plugin/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-2074-to-2.x.

[derek-ho]

Looks like it worked. @DarshitChanpura thank you