Remove pre-deprecation notice for only/except

Merged Jason Yavorska requested to merge jyavorska-master-patch-84082 into master

What does this MR do?

Removes notice that only/except is pre-deprecated, instead directing people to rules as an improvement. If we reach the point where we know are deprecating only/except then we can add a real deprecation notice with actual information in this same place.

Pre-deprecating isn't a well defined state for a feature and this seems to be generating confusion (it's comes across like a notice you should start to worry about it disappearing, minus the actual information you need to prepare).

Related issues

Author's checklist (required)

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

cc @ayufan @nagyv-gitlab @kencjohnston @thaoyeager

Edited by 🤖 GitLab Bot 🤖