Put all RPM tasks in chronological order

Why is this change being made?

Making the task list for the RPM chronological will make it easier to follow, per feedback from various team members who've experienced it over the last 4 to 5 release post cycles.

What does this MR do?

1. cleans up headers, due dates and some task details
2. Moves and add missing due date for General Content Review
3. Moves recurring reminders info to intro section
4. Puts all RPM tasks in chronological order

What does this MR NOT do?

No deleted content, duplicate and/or verbosity of content to be addressed in a separate MR if needed.

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.

---