fix: ensure that globalOnly and stage=global are set together

[jamietanna]

Changes

Context

Please select one of the following:

• This closes an existing Issue, Closes: #
• This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.

• No — I did not use AI for this contribution.
• Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
• Yes — substantive assistance (AI-generated non‑trivial portions of code, tests, or documentation).
• Yes — other (please describe):

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests, but ran on a real repository, or
• Both unit tests + ran on a real repository

The public repository:

[mglazer]

@jamietanna I might have trouble rectifying this change with the recently added allowedUnsafeExecutions. That command needs to have the repository stage, but should be a globalOnly option (since it's not designed to be set at the individual repository level). This seems to break the documentation tests, but probably also breaks other assumptions.

[jamietanna]

Hey @mglazer no worries - I think that the intent behind this change doesn't necessarily work in practice - please ignore this one 😁

(We'd been discussing this on the Renovate Slack and thought that this should be OK, but in practice it doesn't)