Description of problem:

The wrong additional trusted bundle name is reconciled to the CPO deployment in the HCC - https://github.com/openshift/hypershift/blob/369e0f18212b658e0bd6ebe3b9f6f387008ec5bd/hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go#L1291. A user most likely would never run into this using the CLI to create the cluster because it defaults the right name - user-ca-bundle, https://github.com/openshift/hypershift/blob/5ec788802880d550f2164a2210cf90e8d0f32225/api/fixtures/example.go#L501 

Version-Release number of selected component (if applicable):

How reproducible:

Every time

Steps to Reproduce:

1. Create a ConfigMap with a name other than user-ca-bundle for the value to go into the additional-trust-bundle field on a HC yaml spec
2. Deploy the HC yaml spec
3. Observe the CPO fail to deploy

Actual results:

CPO fails to deploy

Expected results:

CPO should deploy

Additional info:

On https://github.com/openshift/hypershift/blob/369e0f18212b658e0bd6ebe3b9f6f387008ec5bd/hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go#L1291, we should pass the name we reconciled here (i.e. user-ca-bundle) https://github.com/openshift/hypershift/blob/248df10f8606696cd284521efccc31471445aa63/hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go#L1755