Update access dropdowns to include related groups

What does this MR do and why?

The access dropdowns use the autocomplete groups endpoint which does not include all the relevant groups in the project. This change is to the use the project groups endpoint for those dropdowns instead.

Contributes to: #345140 (closed)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

1. Create a group
2. Create a subgroup of that group
3. Create a project in the namespace of the subgroup
4. Create another subgroup and invite it to the project
5. Add a user to the project as maintainer
6. Check that relevant groups (the group and 2 subgroups) appear in the dropdown while adding and editing protected branches, protected tags, and protected environments.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #345140 (closed)