Required tasks needed to fully migrate the ACSCS UI codebase to using the Frontend Operator.

This change moves ownership of configuration items like navigation to the ACS UI team (primarily) and allows us to maintain this configuration in our own repository.

From the Slack thread:

https://redhat-internal.slack.com/archives/C023VGW21NU/p1757694028430949?thread_ts=1757694022.226329&cid=C023VGW21NU

From what I can tell, our situation is similar to cost-management in that we both have a nested navigation structure that falls under "OpenShift". I have been using the migration guide and this thread to work through the migration, which I have up in PR on our side here. Can someone confirm or correct my thinking on how we need to proceed from here?
1. Merge our PR to the RedHatInsights/acs-ui repo updating our frontend.yaml
2. Open and merge PRs against chrome-service-backend that add "feoReplacement": "acs.nav" to beta/staging and stable/staging in this area
3. Open and merge PRs against the uhc-portal that replace the acs navigation config with a segmentRef so that our team has ownership of the nested navigation like done for cost-management here
4. Deploy a new build of our app to staging
Test that the navigation looks good on console.stage.redhat.com
Test that there are duplicate entries for ACS under the services dropdown, one from the new FEO config and one from services.json
5. Open and merge PRs against chrome-service-backend that deletes our service dropdown entry for beta/staging and stable/staging from services.json
Test that there is now only a single entry for ACS under the services dropdown
6. Repeat steps 2-5 for beta/prod and stable/prod and ensure everything continues to work as expected
7. Open a final PR against chrome-service-backend to delete our entry from static-services-entries.json