Generate policies and jobs from the new SSOT

What does this MR do and why?

This switches the SSOT from https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/group-definition.yml to https://about.gitlab.com/groups.json to generate the policy files and CI jobs.

The logic was simplified a bit so that there are more assignees to the report issues in general but this makes all reports and their assignments consistent.

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

Action items

• If adding environment variables for reactive processors, update config/triage-web.yaml and .gitlab/ci/triage-web.yml

• (If applicable) Add documentation to the handbook pages for Triage Operations =>

• (If applicable) Identify the affected groups and how to communicate to them:

  • /cc @person_or_group => @gl-quality/eng-prod
  • Relevant Slack channels => #eng-managers, #g_engineering_productivity

  The various team reports generated at https://gitlab.com/gitlab-org/quality/triage-reports/-/issues/ will now use the data from https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/stages.yml (actually consolidated and exposed at https://about.gitlab.com/groups.json). This means you no longer need to edit https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/group-definition.yml to change the assignees of your team reports (you just need to make sure the data in https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/stages.yml is up-to-date). This also means some team will start getting reports created and reports will probably get more people assigned. Please share any feedback in gitlab-org/quality/engineering-productivity/team#358 (closed).

  • Engineering week-in-review

Closes gitlab-org/quality/engineering-productivity/team#343 (closed), #471 (closed).