Draft: Iterate on handbook process change communication

Why is this change being made?

Oftentimes the handbook is leveraged as a way to define and scope processes that teams follow. These processes impact many team members across the organization, yet we do not have a clear and concise way of communicating these changes.

This MR aims to rectify this by creating an MR Template that helps define a lightweight process to help get the word out about a given change.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct 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 in 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.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)