Propose adding all those eligible for IMOC into rotation

Why is this change being made?

Context: I opened https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/17058+ to try to add more eligible IMOC participants by having more folks onboarded. In this next iteration, I am proposing that we schedule all remaining individuals. It's up to each person to finish their onboarding issues. Many of us were added to the rotation originally (6+ months ago) without finishing the onboarding and we seem to be managing fine.

@sgoldstein and I discussed a future iteration of adding more eligible team members to IMOC, and given the need to increase the IMOC pool, this MR proposes adding all of those eligible into the rotation by 2023-02-20. (Date can be adjusted, but I thought it would be best to work within a timeline)

If team members are not ready (e.g. not yet completed their onboarding issues), they can ask to swap with other team members following existing process. This drives higher accountability and a stronger bias for action to complete ongoing IMOC onboarding issues.

Since we have deemed IMOC as a responsibility of all Development and Infrastructure roles in Job Grades 8 and 9, we should make it so and schedule the remaining team members in PagerDuty.

I can further determine a reasonable order to add those remaining. I'll also make sure to ensure those on PTO or any exclusions are captured (e.g. where weekend work may not be enforceable)

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, and the content is SAFE
• 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
  • The when to get approval handbook section explains the workflow in more detail
• 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.

---