Add Issue Wrangler rotation

Why is this change being made?

The Runner team receives a lot of requests for either information or support, and that causes frequent context switching amongst the team. This context switching limits our ability to effectively plan what we can deliver each milestone, and it also can feed into a perception that we are slow to respond based on the number of requests each team member handles.

We've been assigning a weekly "bug wrangler" issue to allow more focus time, however with PTO the rotation still comes around quite quickly. I'm proposing a change to how we handle these incoming requests:

1. We set up a slack automation in the #g_runner channel where engineers can trigger an automated response if a request for help does not have a quick answer.
2. We have a team member assigned each iteration that will only focus on issue wrangling (defined in MR). They will not be assigned any other issues during the iteration but can pull in issues if they have capacity.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---