Improvements to Release Post Merge request template

Why is this change being made?

I am combining all my improvements to the release post merge request template into one for the sake of efficiency and to avoid merge conflicts.

This MR captures several chances that address items in the 13.11 release post retro:

1. #11214 (comment 545044317)
2. #11214 (comment 553793126)
3. #11214 (comment 554142051)

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)