Change granular_scopes history items from GitLab 19.6 to 19.5

What does this MR do?

!260276 (merged) and !260277 (merged) added six history items that say granular_scopes was added to a token response in GitLab 19.6. I wrote 19.6 because I did not expect either of them to make the 19.5 cut, and said in both descriptions that I would change the items to 19.5 if one did. Both merged on 2026-10-08 with milestone 19.5, ahead of the initial 19.5 release candidate that the 19.5 release task schedules for 2026-10-13. This MR changes the six items to GitLab 19.5 and changes nothing else:

• doc/api/groups.md, Rotate a personal access token for an enterprise user (from !260276 (merged))
• doc/api/personal_access_tokens.md, Self-rotate (from !260276 (merged))
• doc/api/user_tokens.md, Create a personal access token (from !260276 (merged))
• doc/api/user_tokens.md, List all impersonation tokens for a user, Retrieve an impersonation token for a user, and Create an impersonation token (from !260277 (merged))

The item that !259764 (merged) added to Self-inform in doc/api/personal_access_tokens.md when it merged on 2026-10-07 already says GitLab 19.5, so after this MR Self-inform and Self-rotate give the same version for the attribute.

!260698 adds a history item directly below the one in List all impersonation tokens for a user, so whichever of the two merges second needs a rebase there. The conflict resolves by keeping the 19.5 line from this MR and the new line from !260698.

Related issues

Related to #632314 (closed) and #632315 (closed), the issues behind !260276 (merged) and !260277 (merged). Both are 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.