Description of problem:
The CVO seems to only report the most recent operator it saw failing to upgrade, not all of them.  This is misleading for admins about why the upgrade is blocked.


See:
https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.0/259/


https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.0/259/artifacts/e2e-aws-upgrade/clusteroperators.json

Shows a number of operators that are still reporting the previous version. (    "version": "4.0.0-0.ci-2019-03-18-152932" is the new version, and  "version": "4.0.0-0.ci-2019-03-18-124953" is the old version). 

But:
https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.0/259/artifacts/e2e-aws-upgrade/clusterversion.json

only indicates the openshift controller manager operator is upgrading:

                    {
                        "lastTransitionTime": "2019-03-18T17:32:56Z",
                        "message": "Cluster operator openshift-controller-manager is still updating",
                        "reason": "ClusterOperatorNotAvailable",
                        "status": "True",
                        "type": "Failing"
                    },
                    {
                        "lastTransitionTime": "2019-03-18T16:43:50Z",
                        "message": "Unable to apply 4.0.0-0.ci-2019-03-18-152932: the cluster operator openshift-controller-manager has not yet successfully rolled out",
                        "reason": "ClusterOperatorNotAvailable",
                        "status": "True",
                        "type": "Progressing"
                    },