Document merge queue bypass for restricted creations

[JanJeter]

Why:

The ruleset documentation explains how the Restrict creations rule works, but it does not mention that merge queue branches also need permission to be created.

When this rule applies to all branches, merge queue branches matching
gh-readonly-queue/{base_branch} can be blocked unless the GitHub Merge Queue app is added to the bypass list.

Closes #45334

What's being changed:

Add documentation explaining that the GitHub Merge Queue app must be added to the bypass list when the Restrict creations rule applies to merge queue branches.

Testing:

• Ran git diff --check.
• Verified that the change is limited to the relevant ruleset documentation.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.