Retry/Rerun PR Autocherrypick post merge

[jyejare]

Problem Statement

Following are the scenarios when we were not able to rerun the Merged PRs AutoCherrypick:

• Autocherrypicking failed due to OOM/unidentified_abort during ACP GHA run
• Missed adding the version label while autocherrypicking for a specific version
• Retry of AutoCherrypicking of a big PR when failed with conflicts due to others didn't cherry-pick the changes. Now we could ask others to fix their cherrypicks and simply retry the big PRs ACP from this GHA.
• Bulk PRs cherry-pick in about to depreciate branch, but need the branch for immediate testing or for multiple reasons
• etc

Solution

• We should be able to handle all the above scenarios now with the new standalone Retry Merged PRs AutoCherryPick

Related PR:

• Support Given Pull Requests (from param) AutoCherrypick and more jyejare/github-cherry-pick-action#42 Allows to take PR number as an input for cherry-picking

Tip:

Do as many retries as you want and we wont create issues for failures, because you will have one already from original AutoCherryPick GHA. Good Luck 👍

Example usage:

• Go to Actions tab in Robottelo Github Repository
• Select Retry Merged PRs AutoCherryPick GHA from left pane.
• Choose to run the workflow from the dropdown in the right corner.
• Select a branch to run the workflow from or where the PR exists for cherry-picking. E.g master to cherry-pick from stream branch
• Next, enter parent PR number
• Next, comma-separated list of branches to cherry-pick the PR into.

Testing (Success) :

https://github.com/jyejare/test-acp/actions/runs/9661992453/job/26651194469

[vijaysawant]

• Adding comments/suggestions based on my understanding about use of apostrophe
• Use of correct form for word PRs & PR's

PRs: Plural form (correct usage for multiple Pull Requests)
PR's: Possessive form (correct usage for indicating something that belongs to a single Pull Request)

[omkarkhatavkar]

LGTM, minor enhancements

[jyejare]

@vijaysawant I could only make changes of apostrophe in description field, rest are identifiers of actions so cant use there.