rerun-workflow.yml: add support for rerunning failed jobs only

[bevanjkay]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• Checked the cask is submitted to the correct repo.
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

This adds the ability for ci-requeue-failed-jobs and ci-retry-failed-jobs labels to be used, that re-run only the failed jobs instead of the whole test suite. It is useful for re-running failed jobs using the label, or in the few cases where we have flaky upstream servers, it can be difficult to get all the jobs to complete with ci-retry, this enables us to only retry the jobs that failed on a schedule.

Labels have not yet been added.

[carlocab]

Seems reasonable to me, but I wonder if we should find another way given Homebrew/brew#17378

[bevanjkay]

Yes possibly. I just added the option to Markus' workflow upstream though 😢

[carlocab]

You can always see if Markus is willing to migrate them to https://github.com/Homebrew/actions

[bevanjkay]

@carlocab How would you feel about merging this for now, so that it's available until we find a way to replace it?

[carlocab]

I'm ok with that, but I don't have ✅ (only ✔️)