Deployment approval group members are not visible to project members

Summary

When a project add a group as a member and add that group as deployment approver of an environment. The member of the project cannot see the approvers.

Steps to reproduce

1. Have a project for deployment to an environment (i.e. prod)
2. Invite a group as a member of the project
3. Protect the prod environment and add the group as approver
4. Make changes and try to deploy to the environment
5. Navigate to the relevant https://example.gitlab.com/path/to/project/-/environments/:id/deployments/:id

Observe the Requires 1 approval but it doesn't mention who the approver is.

Probably similar to Approval group members are not visible to MR cr... (#368487)

Example Project

What is the current bug behavior?

Project members have no visibility of deployment approver if they were added through group that they don't have access to.

What is the expected correct behavior?

The project member see deployment approvers on the deployment page

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes