Use SAML Groups as CODEOWNERS
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=373131)
</details>
<!--IssueSummary end-->
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
We're a company who like many others federated user identity into GitLab from an external IDP (e.g. AAD, Okta, Ping, OneLogin etc.) and provision access to users using Role Based Access Control (RBAC). Basically we create user groups that map to organisational roles. We ideally would be able to dictate the access of our users as much of possible in GitLab, and our repos, from the SAML groups that are pushed with the user when they federate in from SSO.
Specifically, it would be extremely useful if we could reference those SAML groups in CODEOWNERS files. In this way we would not need a complex re-mapping of our organisational structure into GitLab's groups in order to make sure that only those in the MYCORP-SECURITY user group can approve changes to any `aws-security-group` terraform file (for example) across multiple repos/gitlab groups.
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
-->
<!-- Label reminders
Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
issue