Document blank issue access for maintainers when blank_issues_enabled is false

When blank_issues_enabled is set to false, users with write access or above
(Write, Maintain, Admin) now still see the 'Blank issue' option in the
template chooser with a 'Maintainers only' label. Contributors with Read
or Triage access continue to only see configured templates.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: sunnyi101

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md

@@ -65,6 +65,9 @@ Here is the rendered version of the issue form.
 
 You can encourage contributors to use issue templates by setting `blank_issues_enabled` to `false`. If you set `blank_issues_enabled` to `true`, people will have the option to open a blank issue.
 
+> [!NOTE]
+> When `blank_issues_enabled` is set to `false`, users with write access or above (Write, Maintain, or Admin roles) will still see the "Blank issue" option in the template chooser, labeled "Maintainers only." This allows maintainers to bypass template restrictions when needed. Contributors with Read or Triage access will only see the configured templates.
+
 > [!NOTE]
 > If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your _config.yml_ file, the template in `issue_template.md` will be used when people choose to open a blank issue. If you disable blank issues, the template will never be used.