Fix CE/EE separation of code in groups access dropdown
What does this MR do and why?
In !229920 (comment 3237373307) we noticed that the code in app/assets/javascripts/groups/settings/api/access_dropdown_api.js was not split up between CE and EE correctly. Also the autocomplete routes were defined using Gitlab.ee instead of being separated in the ee directory which makes it so the JavaScript path helpers are not generated in the correct place. This MR fixes both of these problems by moving the routes to an ee directory and moving app/assets/javascripts/groups/settings/api/access_dropdown_api.js and app/assets/javascripts/groups/settings/components/access_dropdown.vue to ee because they are only used in ee.
app/assets/javascripts/projects/settings/api/access_dropdown_api.js has the same problem but to keep this MR smaller I will fix this one in a follow-up MR.
Screenshots or screen recordings
Routes
Order is different, but same routes
| Before | After |
|---|---|
 |
 |
Protected environments
Still the same
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- Go to a premium or ultimate group -> Settings -> CI/CD
- Open dev tools -> Network
- In the Protected environments section click
Protect an environment - Select a tier
- Inspect network requests
- Verify dropdowns still work
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.