Release Post revisions to timing and What's New MR instructions

Why is this change being made?

This MR fixes a few todos that cause confusion for the release post manager:

• The “Incorporate feedback” section is updated to reflect the amount of time allowed for executive review and feedback
• "Creating the What's New MR" is given its own section
• Timing expectations are added (15:00-19:00 UTC) into “What’s New” backend_maintainers message, so people in the right time zone can volunteer.
• SaaS-only features need to use [free, premium, ultimate] in the "What's New" MR

Related to #13922 (closed)

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.
• 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
• 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.

---