TALM creates manageclusterview objects for every SNO during platform and operator upgrade upfront although it doesn't need them until much later

While attempting to upgrade both the platform and operators of 2340 SNOs, I found that TALM is creating all managedclusterview objects for "operator" upgrade first although this occurs after the platform is upgraded.  This seems wasteful because if a cluster fails to upgrade, we won't need to have the MCV objects anyhow. On top of that, MCVs are created only for non compliant clusters at the time, which can be a very different list before and after the platform upgrade. Any cluster that becomes non compliant later doesn't get the install plan approval due to the missing MCV. 

Hub OCP 4.11.12
SNO OCP 4.10.32 upgrading to 4.11.5

1.
2.
3.

2022-11-03T15:11:45.522Z	INFO	multiCloudLog	[EnsureManagedClusterView] MCV doesn't exist, create it	{"name": "complete-upgrade-4.11.5-0000-ztp-platform-upgrade-subscription-sriov-network-operator-subscription-47nql", "namespace": "sno00001"}
2022-11-03T15:11:45.529Z	INFO	multiCloudLog	[EnsureManagedClusterView] MCV doesn't exist, create it	{"name": "complete-upgrade-4.11.5-0000-ztp-platform-upgrade-subscription-sriov-network-operator-subscription-47nql", "namespace": "sno00002"}
2022-11-03T15:11:45.537Z	INFO	multiCloudLog	[EnsureManagedClusterView] MCV doesn't exist, create it	{"name": "complete-upgrade-4.11.5-0000-ztp-platform-upgrade-subscription-sriov-network-operator-subscription-47nql", "namespace": "sno00004"}
2022-11-03T15:11:45.543Z	INFO	multiCloudLog	[EnsureManagedClusterView] MCV doesn't exist, create it	{"name": "complete-upgrade-4.11.5-0000-ztp-platform-upgrade-subscription-sriov-network-operator-subscription-47nql", "namespace": "sno00005"}