Give everyone with git.drupalcode.org commit access to all issue forks

Currently everyone must get push access to each individual issue fork repository. This workflow was originally set up as a "speed bump" to discourage mass-updating all issue forks.

As we move toward moving issues to GitLab, #3250923: GitLab Collaboration Workflow: Enable GitLab issues and forking into the 'issue' namespace, with shared access across the community → , the issue fork workflow will be similar. GitLab does not allow injecting UI elements, so we can’t put the same button on the GitLab issue page. We could have a bot people can summon to get access, but that would be clunky and noisy. Or we could keep our own UI on Drupal.org to get access, which would be clunky.

Instead of trying to keep this functionality, we can remove the need for it. Issue forks are in the https://git.drupalcode.org/issue group. We can give everyone with group-level access and that will allow access to every issue fork.

Tasks

• See what happens for email notifications when someone is added to the group. Turn off notifications if needed & possible.
• ✅ done - Write MR which automatically adds people to the group when they get a new git.drupalcode.org account.
• 🔄 in progress - Write bulk update to add existing people top the group.
• Add integrity check for everyone being in the group,
• Write MR to remove “Get push access” button and related functionality.

Deployment

1. Deploy changes to add new git.drupalcode.org users to the https://git.drupalcode.org/issue group.
2. Bulk update to add all existing users to the issue group.
3. Deploy changes to remove “Get push access” button and related functionality.