Since swapping over to the FEO, there's a mismatch of information between the frontend.yaml of rbac-ui and the nav files in chrome. To get around this, we can add the 'iam' bundle to the `FEO_BUNDLES_ONBOARDED_IDS` in the chrome config. Before doing this, we have to verify that the iam config looks correct before adding this (since it contains more than just rbac-ui).

From bflorkie@redhat.com: "We should verify that all iam config looks correct on stage in the generated FEO config before flipping this on. This should be easy to do - simply compare what is in the legacy config here: https://github.com/RedHatInsights/chrome-service-backend/blob/main/static/stable/stage with what the FEO is generating here in the feo-context-cfg config map here: https://console-openshift-console.apps.crcs02ue1.urby.p1.openshiftapps.com/k8s/ns/chrome-service-stage/configmaps/feo-context-cfgFor example, in the case of navigation files, compare https://github.com/RedHatInsights/chrome-service-backend/blob/main/static/stable/stage/navigation/iam-navigation.json to what you see in https://console-openshift-console.apps.crcs02ue1.urby.p1.openshiftapps.com/k8s/ns/chrome-service-stage/configmaps/feo-context-cfg > bundles.json key > nested object with id iam
 and ensure there are no missing entries and that the ordering seems correct.