Update Certify Group Maturity Dates

This MR proposes changes in Maturity target dates for RM and QM for groupcertify .

The targets, from Certify Product Manager @mmacfarlane 's digging, were proposed a few years back, and given the pause on Certify work, creation, dissolution, then a recreation of the team are not achievable as originally estimated. Example being, the dates had a target of Viable maturation for RM by 2023-01-01. That date has passed already and we have not met the Viable maturity scale as set in this Epic.

Maturity dates have been adjusted for Viability based on the timeline in which work was paused, with subsequent Maturity targets adjusted as well with the same development timeline gaps.

Why is this change being made?

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.

---