Documentation update for breaking changes in 16.0

What does this MR do and why?

We have 2 different breaking changes going out on 16.0, and on May 8th, 2023 on gitlab.com. Before that, we would need to address this in the documentation, which is what this MR does:

2 rollout issues are:

• #393622 (closed)
• #391922 (closed)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

changed milestone to %16.0

added grouptenant scale typemaintenance labels

assigned to @manojmj

added devopsdata stores sectioncore platform labels

added docs-only label

added 1 commit

• c01eca1d - Doc changes for Projects List API

Compare with previous version

mentioned in issue #391922 (closed)

added documentation label

	1 Warning
	Please add a merge request subtype to this merge request.

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/security/rate_limits.md (Link to current live version)
• doc/user/admin_area/settings/rate_limit_on_projects_api.md (Link to current live version)
• doc/user/admin_area/settings/visibility_and_access_controls.md (Link to current live version)
• doc/user/gitlab_com/index.md (Link to current live version)
• doc/user/group/manage.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added 1 commit

• acd0bbca - Doc changes for always perform delayed deletion

Compare with previous version

mentioned in issue #393622 (closed)

changed the description

marked this merge request as ready

changed the description

added 1 commit

• 834e5c6e - Make some changes

Compare with previous version

added 1 commit

• f4f8d59a - Make some changes

Compare with previous version

marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

@lciutacu could you please review?

cc @lohrc these are our doc updates for the breaking changes.