Description of the problem:
While working on implementing capability disabling in HyperShift, specifically for the Console capability, I came across the following manifests that appear to be related to the Console but are missing the capability.openshift.io/name: Console annotation:

# grep -L 'capability.openshift.io/name: Console' /tmp/release/*console*.yaml
/tmp/release/0000_10_config-operator_01_consoles.crd.yaml  
/tmp/release/0000_50_console-operator_00_helmchartrepositories.crd.yaml  
/tmp/release/0000_50_console-operator_00_projecthelmchartrepositories.crd.yaml  
/tmp/release/0000_50_console-operator_07-operator-ibm-cloud-managed.yaml  
/tmp/release/0000_50_console_01_consoles.crd.yaml  
/tmp/release/0000_90_console-operator_03_console_plugin_storage_migration.yaml

How reproducible:

Always

Steps to reproduce:

I wasn't able to reproduce it in standalone openshift cluster.
Discussion about it is here - https://redhat-internal.slack.com/archives/C6A3NV5J9/p1748934399821169

To reproduce it in hypershift, need to use the code in the following draft PR - https://github.com/openshift/hypershift/pull/6183

build CPO image + hypershift CLI and use those in order to create HostedCluster with disable capabilities option, where the Console is in the list.

Actual results:
Resources missing the required annotation are still present even when the Console capability is disabled.
Expected results:

These resources should not appear when the Console capability is disabled, as their presence could lead to a misleading UX.