Proposed title of this feature request

Surface control-plane operator errors in HostedControlPlane conditions

What is the nature and description of the request?

When the control-plane operator pod has trouble reconciling its operands, it should report the trouble in HostedControlPlane status.conditions.

Why does the customer need this?

Currently, issues that block HCP progress could be buried in logs, which may require the intervention of HyperShift developers to debug. By surfacing persistent issues in HostedControlPlane conditions, and possibly bubbling them up to HostedCluster conditions, the controllers become more transparent and accessible, and more responders will be able to self-serve triage, analysis, and recovery.

Similar work:

• RFE-5638 asked for a way to bypass checkOIDCPasswordGrantFlow. OCPBUGS-37753 delivered a more reliable check, but doesn't seem to have delivered a way to bypass a failing check, or a conditions entry that reports when the check is failing.
• HOSTEDCP-2174 is asking for conditions reporting from the hosted-cluster-config-operator pod. This RFE is requesting similar work in the control-plane operator pod.

Specific example:

A 4.14.39 control-plane operator pod stuck on this HostedControlPlaneReconciler.reconcile Reconciling OpenShift OAuth API Server error, which blocked progress on a 4.14.38 to 4.14.39 update, but there was no mention of the error in HostedControlPlane status.  Possibly the issue is related to OCPBUGS-44236, but this RFE is asking for "make these kinds of issues easier to notice and debug when they happen" and not "fix a specific instance of this issue class".

List any affected packages or components.

HyperShift, control-plane operator