Note merge queue plan availability in "Managing a branch protection rule" (#46523)

Co-authored-by: subatoi <32935794+subatoi@users.noreply.github.com>

Author: Kiddo4993

content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule.md

@@ -74,7 +74,11 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 1. Optionally, select **Require conversation resolution before merging**.
 1. Optionally, select **Require signed commits**.
 1. Optionally, select **Require linear history**.
-1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %}
+1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**.
+
+   > [!NOTE]
+   > {% ifversion fpt or ghec %}Pull request merge queues are available in any public repository owned by an organization, or in private repositories owned by organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}{% elsif ghes %}Pull request merge queues are available in any organization-owned repository on {% data variables.product.prodname_ghe_server %}.{% endif %} {% data reusables.pull_requests.merge-queue-references %}
+
 1. Optionally, to choose which environments the changes must be successfully deployed to before merging, select **Require deployments to succeed before merging**, then select the environments.
 1. Optionally, make the branch read-only.
    * Select **Lock branch**.