Update MR template to require/document transparency announcement

Why is this change being made?

Context in this Slack thread. This is to encourage team members to be as transparent as possible when making changes that impact other team members.

All MRs to help increase transparency

• Add requirements for controlled docs reviewers ... (!127695 - merged)
• Make default template instructions more clear, ... (!127834 - merged)
• Update MR template to require/document transpar... (!127707 - merged)

Related issues

1. Updates to handbook pages which have a large im... (gitlab-com/content-sites/handbook#90)
2. #32287 (comment 1378655775)

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---