Add User#full_private_access? to check if user has access to all private groups & projects
What does this MR do?
In CE only the admin has access to all private groups & projects. In EE also an auditor can have full private access.
To overcome merge conflicts, or accidental incorrect access rights, abstract this out in
User#admin? now only should be used for admin-only features. For private
User#full_private_access? should be used.
Are there points in the code the reviewer needs to double check?
Any other situations where this method should be used?
I searched the EE codebase for the use of
admin_or_auditor? and replaced those.
Why was this MR needed?
Backported from gitlab-org/gitlab-ee!2199
Does this MR meet the acceptance criteria?
- Changelog entry added, if necessary
- Documentation created/updated
- API support added
- Added for this feature/bug
- All builds are passing
- Conform by the merge request performance guides
- Conform by the style guides
Branch has no merge conflicts with
master(if it does - rebase it please)
- Squashed related commits together
What are the relevant issue numbers?
Closes #31745 (closed).