Extend the Control Plane Informer in the Update Status Controller so it takes ClusterOperator resources into account and fully populates the ClusterVersion status insight.

The actual API structure for an update status insights needs to be taken from whatever state https://github.com/openshift/api/pull/2012 is at the moment. The story does not include the actual API form nor how it is exposed by the cluster (depending on the state of API approval, the USC may still expose the API as a ConfigMap or an actual custom resource).

After the Control Plane Informer is able to track and interpret the state of ClusterOperator resources (OTA-1411), it will be possible to bring the rest of the client-side prototype logic to the Status API / Control Plane Informer and fully populate the ClusterVersion status insight.

The expectations for ClusterVersion status insight are described in the design doc.

Definition of Done

• Outside of update, the CV status insight has an Updating=False condition, and the remaining fields (versions, started, completed, assessment and completion) reflect the last update the control plane underwent. estimate is not present.
• During the update:
  • insight has Updating=True condition
  • versions correspond the the current update (=match the current CV history item)
  • startedAt corresponds to how current oc adm upgrade status computes it
  • completedAt is empty
  • estimatedCompletedAt corresponds to how current oc adm upgrade status computes it, but hopefully is more precise because it knows when the last updated CO finished updating
  • assessment corresponds to how current oc adm upgrade status computes it
  • completion corresponds to how current oc adm upgrade status computes it