[CI] Repeated PRs by registry auto-update script can cause problems

[chalin]

For context see #5119 (comment).

In summary,

• Auto-update registry versions (88aedc112b2588e0acf45d4623c849e0f8264928) #5114 was on hold because it broke link checking

The auto-update script issues a new PR:

• Auto-update registry versions (49a605df5a62461493877154c3bc9591c2969c8f) #5119

Unbeknownst to Phil, he ran a fix command, and got a green light from GH to merge, so he merged; but that broken link checking. I've followed up with

• [CI] After a fix:* command, tell user to rerun full checks #5122

but I'm opening this issue / discussion to explore if there is a way to "pause" the registry auto-update to avoid a similar problem? If there is a (relatively easy) way, then the question is: do we want to use such a pause feature. Note that the OTel package version update script will not reissue a new PR. I know that the situation is different here, but if we could have a similar behavior: don't issue a new registry auto-update PR if there is one that is already open?

[svrnm]

Dependabot and Renovate do it in a way that they check for existing PRs and update them accordingly (or close them and open new ones). I did it the way it is right now, because it was just "the easy solution". Let me see if and how this can be improved