Allow retry commands to be used in distribution groups

What does this MR do and why?

Closes Expand retry_job and retry_pipeline commands in... (#1428 - closed)

The MR adds the following behavior to the retry_job and retry_pipeline commands:

1. Allow additional projects to use these commands. See project list noted in gitlab-org/distribution/team-tasks#1338 (comment 1581662492)
2. In these additional projects, the only people that can invoke the commands are team members from groupdistribution

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 =>
  • Relevant Slack channels =>
  • Engineering week-in-review