1. Proposed title of this feature request: Disabled Capabilities at install time
2. What is the nature and description of the request? During HCP installation, today only image-registry (https://hypershift-docs.netlify.app/reference/api/#hypershift.openshift.io/v1beta1.OptionalCapability) can be disabled. However, OCP supports disabling more capabilities such as Console and Ingress Operator (https://issues.redhat.com/browse/OCPSTRAT-346) . OCP documentation is available https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/installation_overview/cluster-capabilities#enabling-cluster-capabilities_cluster-capabilities 
3. Why does the customer need this? (List the business requirements here)

Running these operators on each clusters is redundant. Customers either use services in the public cloud or these operators centrally in hub-spoke architecture. Separate subnet is designated as network ingress or edge subnet with additional firewall, observability and governance applied.   

Operators and the workloads of these capabilities run on worker nodes so they cost infrastructure and subscription fees. 

These operators need to be 'separated out' from rest of the applications for QoS, adding extra operational overhead. Control Plane upgrades are still tied to the states of the Cluster-Operators and worker nodes, that it makes it hard to operationalize upgrades of HCP And worker nodes separately. 

4. List any affected packages or components.

Hosted Control Plane