kubevirt: Suspected regression in kubevirt v0.53.0-rc.0 (live migration on upgrade)

What happened: When trying to consume the newly released kubevirt v0.53.0-rc.0 in HCO, all upgrade tests were failing because the virt-launchers were not upgraded on kubevirt upgrade, despite having LiveMigrate on .spec.workloadUpdateStrategy.workloadUpdateMethods at KubeVirt CR. As a result, post-upgrade there are VMIs with kubevirt.io/outdatedLauncherImage label that are still running. The VM that is being used in the test is defined here: https://github.com/kubevirt/hyperconverged-cluster-operator/blob/main/hack/vm.yaml which is live-migratable.

What you expected to happen: All live-migratable VMsvirt-launchers should be upgraded, and not VMIs withkubevirt.io/outdatedLauncherImage` label should be present on the cluster post-upgrade.

How to reproduce it (as minimally and precisely as possible): Constantly failing on all upgrade lanes over multiple cloud providers in the CI of: https://github.com/kubevirt/hyperconverged-cluster-operator/pull/1918

Additional context: Add any other context about the problem here.

Environment:

• KubeVirt version (use virtctl version): v0.53.0-rc.0
• Kubernetes version (use kubectl version) :v1.23.3-2047+d464c70a480f1c-dirty
• VM or VMI specifications: link
• Cloud provider or hardware configuration: AWS, Azure and GCP
• OS (e.g. from /etc/os-release): N/A
• Kernel (e.g. uname -a): N/A
• Install tools: N/A
• Others: N/A