Description of problem:
In the case of using MCE/Hypershift on BM (As opposed to AWS provider) and using agent based hosted control planes, there is no need for s3 secret "hypershift-operator-oidc-provider-s3-credentials", yet the hypershift operator pod will not deploy without the s3 secret set.


Version-Release number of selected component (if applicable):
Latest MCE2.0 downstream snapshot
OCP 4.10.x hub cluster

How reproducible:
100%

Steps to Reproduce:
1. Ensure hub cluster has a managedcluster resource
2. Create managedclusteraddon, referencing hub managedcluster
oc apply -f - <<EOF
apiVersion: addon.open-cluster-management.io/v1alpha1
kind: ManagedClusterAddOn
metadata:
  name: hypershift-addon
  namespace: local-cluster   # name of managed cluster
spec:
  installNamespace: open-cluster-management-agent-addon
EOF

3. Check managedclusteraddon status in the local-cluster namespace

Actual results:
Hypershift addon remains unknown

oc get managedclusteraddon -n local-cluster
NAME               AVAILABLE   DEGRADED   PROGRESSING
hypershift-addon   Unknown                
work-manager       True           


Expected results:
AVAILABLE moves to true and hypershift operator deploys in hypershift operator name space

Additional info:

## If I do not create the S3 key: 


# hypershift-addon shows the following errors and stays unknown
 oc get managedclusteraddons.addon.open-cluster-management.io 
NAME               AVAILABLE   DEGRADED   PROGRESSING
hypershift-addon   Unknown                
work-manager       True       


    Last Transition Time:  2022-05-27T17:16:57Z
    Message:               The status of hypershift-addon add-on is unknown.
    Reason:                ManagedClusterAddOnLeaseNotFound
    Status:                Unknown
    Type:                  Available


# Hypershift addon gent pod tries to launch hypershift with the s3 secret, but the second is not created so hypershift never runs.

oc logs -f hypershift-addon-agent-5499c58967-cz8vk -n open-cluster-management-agent-addon                                                                                                                                                                   
I0527 17:24:17.124602       1 request.go:665] Waited for 1.028914334s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/operators.coreos.com/v1alpha2?timeout=32s                                                              
2022-05-27T17:24:23.698Z        INFO    agent.agent-reconciler  agent/hypershift.go:192 enter runHypershiftInstall                                                                                                                                                              
2022-05-27T17:24:23.715Z        ERROR   agent.agent-reconciler  agent/hypershift.go:206 failed to get bucket secret(local-cluster/hypershift-operator-oidc-provider-s3-credentials) from hub, will retry.       {"error": "secrets \"hypershift-operator-oidc-provider-s3-creden
tials\" not found"}                                                               [...]
2022-05-27T17:24:23.715Z        INFO    agent.agent-reconciler  agent/hypershift.go:207 exit runHypershiftInstall
2022-05-27T17:24:23.715Z        ERROR   agent.agent-reconciler  agent/hypershift.go:103 failed to run hypershift cmd    {"error": "secrets \"hypershift-operator-oidc-provider-s3-credentials\" not found"}