`restrict-creations` should warn about compatibility with merge queues

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#restrict-creations

What part(s) of the article would you like to see updated?

Restrict creations

Explain that you need to add the GitHub Merge Queue app to the bypass list if you apply the rule to "all branches" (or anything that would match the github merge queue branch pattern)

• Merge queue doesn't work if creation of new branches is forbidden community/community#167530

Additional information

The github merge-queue prefix appears to be documented as gh-readonly-queue/{base_branch}:

docs/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md

Line 49 in 6835268

With third-party CI providers, you will need to update your CI configuration to run when a branch that begins with the special prefix `gh-readonly-queue/{base_branch}` is pushed to. These are the temporary branches that are created on your behalf by a merge queue and contain a different `sha` from the pull request.

[Sharra-writes]

@jsoref Not sure if this is related to the issue about bypass lists that was opened earlier, but it's the same team, at least, so I've given it to them.

[github-actions]

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀

[github-actions]

This is a gentle reminder for the Technical Content team that this issue is waiting for technical review by a subject matter expert (SME).