Quote role names in rulesets

[janbrasna]

[WIP] changes requested see #31686

Why:

The sentence reads somewhat puzzling until you realize those are "token" roles. Quoting them, and making them capitalized to distinguish it's not a ordinary word but a "term" helps readability.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Occurrences of maintain and write roles in rulesets reusables changed to "Maintain" and "Write".

Older docs use emphasis Write and Maintain but that has since been used solely for CTA/UI elements to activate, so while visually better looking a more basic quoting + capitalization was chosen.

Reusable usage:

• prod: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#granting-bypass-permissions-for-your-ruleset
• pr: https://docs-31532-e071fe.preview.ghdocs.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#granting-bypass-permissions-for-your-ruleset

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[nguyenalex836]

@janbrasna Thanks so much for opening a PR! I'll get this triaged for review ✨

[janbrasna]

• I've followed https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#permissions that mentions "Write" or "Admin" in resources as the way to quote and capitalize the names.
• However the accompanying examples right after the definition in Style guide don't follow the set rules.
• I've therefore opened an issue Style guide for access, permission, role names and its usage unclear #31686 to clarify this.