For each project access token created, a project bot user is created
and added to the project

GitLab docs explain how to create a group access token manually.
https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html#group-access-token-workaround

If a project is under the group that has SSO enforcement enabled, it
won't allow to add a user not linked to the SAML account as a member of
this project. It didn't allow to create project access token for a
project under SSO enforcement since project bot users are not supposed to be
linked SAML account.
It was fixed in https://gitlab.com/gitlab-org/gitlab/-/commit/f9df9d2f97f091a4633ee8497e81921e4d6ebfff

I [noticed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74240/diffs#307d381390eea67e67da59bea05d1f657b9b8e5d_22_25)
that we have the same issue on creating group access token.
https://app.slack.com/client/T02592416/CLM1D8QR0

This change makes it possible to create group access token for a group
that has SSO enforcement enabled.

Changelog: fixed
EE: true