Add a word list exception for right-click

• Please check this box if this contribution uses AI-generated content as outlined in the GitLab DCO & CLA.

What does this MR do?

Marcel sent !153561 (merged) to me overnight, proposing a bugfix to SubstitutionWarning.yml for the string right-click, which was getting caught in the test for click.

My original commit to this MR probably won't be what we end up merging into the word list; it's intended to start the discussion. Google and Microsoft differ in their recommendations:

• Google is more OK with click than historically we've been: https://developers.google.com/style/word-list#click
• Microsoft prefers select and hold (or right-click) for actions that are not necessarily mouse-specific: https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/r/right-click

If we go with Microsoft's guidance, we'd still need the bugfix to allow right-click in SubstitutionWarning.yml.

Related issues

• Related to Ignore click when preceeded by right- (!153561 - merged)
• Related to The vale substitution rule for "click" has fals... (#386505 - closed)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.