Adding info about the July change for Non-expiring access tokens

What does this MR do?

From discussion in https://gitlab.slack.com/archives/CLM1D8QR0/p1729604767010409

The customer in ZD ticket was confused about the difference in this deprecation notice and the blog post - Why GitLab access tokens now have lifetime limits

Related issues

Documentation updates to reflect the revised status of token expiration

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.

data/deprecations/15-4-non-expiring-access-tokens.yml

@@ -4,6 +4,32 @@
   breaking_change: true
   reporter: hsutor
   body: |  # Do not modify this line, instead modify the lines below.
+    Whether your existing project access tokens have expiry dates automatically applied depends on what GitLab offering you have, and when you upgraded to GitLab 16.0 or later:
+
+    - On GitLab.com, during the 16.0 milestone, existing project access tokens without an expiry date were automatically given an expiry date of 365 days later than the current date.
+    - On GitLab self-managed, if you upgraded from GitLab 15.11 or earlier to GitLab 16.0 or later:
+      - On or before July 23, 2024, existing project access tokens without an expiry date were automatically given an expiry date of 365 days later than the current date.
+        This change is a breaking change.
+      - On or after July 24, 2024, existing project access tokens without an expiry date did not have an expiry date set.
+
+    On GitLab self-managed, if you do a new install of one of the following GitLab versions, your existing project access tokens do not have expiry dates automatically applied:
+
+    - 16.0.9
+    - 16.1.7
+    - 16.2.10
+    - 16.3.8
+    - 16.4.6
+    - 16.5.9
+    - 16.6.9
+    - 16.7.9
+    - 16.8.9
+    - 16.9.10
+    - 16.10.9
+    - 16.11.7
+    - 17.0.5
+    - 17.1.3
+    - 17.2.1
+
     Access tokens that have no expiration date are valid indefinitely, which presents a security risk if the access token
     is divulged. Because access tokens that have an expiration date are better, from GitLab 15.3 we
     [populate a default expiration date](https://gitlab.com/gitlab-org/gitlab/-/issues/348660).