Improve community contribution MR discovery and coaching

This was brought up organically by @joshlambert that some of the MRs for devopsverify from the community are building up. Some of them being almost 1 year.

Josh: We have a huge backlog of community contributed MR’s in Verify (specifically Runner) of over 100 (~20% of total). This is proving to be a very frustrating experience, not just contributors but also paying customers: gitlab-org/gitlab-runner!1041 (comment 202338266). => Josh: Mek, can we add the backlog of community MR’s to triagebot and quality dashboard? => Mek: We already have a Community Contribution triage package, I‘ll follow up on making improving the format.

We have community MR triage packages for MRs already https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#community-merge-requests-requiring-attention

This seems to only be active for GitLab CE & GitLab EE I think we should expand this to other core projects e.g.

• Gitaly - https://gitlab.com/gitlab-org/quality/triage-ops/pipeline_schedules/29055/edit
• Runner - https://gitlab.com/gitlab-org/quality/triage-ops/pipeline_schedules/29680/edit

Other improvements:

• Consider adding Community contribution to this type of triage report so we can filter on ~"triage-package" and Community contribution => !260 (merged)
  • https://gitlab.com/gitlab-org/gitlab-ce/issues/58131
• Spell out the names of these triage reports. Instead of Merge requests requiring attention call it Community Contributions MR report => !260 (merged)
• Add a daily report for untriaged 'Community contribution' MRs: !592 (merged)
• Draw attention to EMs for Community contribution based on a ~group:: label: #565 (closed) => !622 (merged)
• Post these Community Triage package on the #mr-coach channel