CLOUDP-298184 - release notes for telemetry (#4132)

# Summary

WIP related docs PR:
https://github.com/10gen/docs-k8s-operator/pull/2063/files

## Proof of Work

## Checklist
- [x] Have you linked a jira ticket and/or is the ticket in the title?
- [x] Have you checked whether your jira ticket required DOCSP changes?
- [x] Have you checked for release_note changes?

## Reminder (Please remove this when merging)
- Please try to Approve or Reject Changes the PR, keep PRs in review as
short as possible
- Our Short Guide for PRs:
[Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- Remember the following Communication Standards - use comment prefixes
for clarity:
  * **blocking**: Must be addressed before approval.
  * **follow-up**: Can be addressed in a later PR or ticket.
  * **q**: Clarifying question.
  * **nit**: Non-blocking suggestions.
  * **note**: Side-note, non-actionable. Example: Praise
  * --> no prefix is considered a question

---------

Co-authored-by: Dan Mckean <[email protected]>

Author: 2 people

RELEASE_NOTES.md

@@ -3,6 +3,11 @@
 # MongoDB Enterprise Kubernetes Operator 1.32.0
 
 ## New Features
+* Adding opt-out anonymized telemetry to the operator. The data does not contain any Personally Identifiable Information
+  (PII) or even data that can be tied back to any specific customer or company. More can be read [here](https://www.mongodb.com/docs/kubernetes-operator/current/reference/meko-telemetry), this link further elaborates on the following topics:
+  * What data is included in the telemetry
+  * How to disable telemetry
+  * What RBACs are added and why they are required
 * **MongoDB**: To ensure the correctness of scaling operations, a new validation has been added to Sharded Cluster deployments. This validation restricts scaling different components in two directions simultaneously within a single change to the YAML file. For example, it is not allowed to add more nodes (scaling up) to shards while simultaneously removing (scaling down) config servers or mongos. This restriction also applies to multi-cluster deployments. A simple change that involves "moving" one node from one cluster to another—without altering the total number of members—will now be blocked. It is necessary to perform a scale-up operation first and then execute a separate change for scaling down.
 
 ## Bug Fixes