#55396: ci: improve idempotence of release board creation workflow
Description of Change
We've been hitting persistent errors from GitHub that we're trying to work around, so making this workflow more idempotent for re-runs to get to the later steps after a failure is useful (particularly backfilling merged PRs). This isn't meant to be exhaustive and able to recover from any sort of partial failure that GitHub might throw at us, just good enough to be safe to re-run as needed.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
Release Notes
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron