As this issue is also seen with CNV 4.14 interim builds, cloning this bug to CNV 4.14 as well

+++ This bug was initially created as a clone of Bug #2087608 +++

Description of problem:
------------------------
When the HCO CR is deleted and created back, HCO CR was not reaching a stable condition

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
CNV 4.11 ( bundle - v4.11.0-360 )
Index Image - registry-proxy.engineering.redhat.com/rh-osbs/iib:233912
hyperconverged-cluster-operator - v4.11.0-65
OCP 4.11 nightly ( 4.11.0-0.nightly-2022-05-11-054135 )

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Set the 'uninstallStrategy' of HCO CR to 'RemoveWorkloads'

1. oc edit hco kubevirt-hyperconverged -n openshift-cnv

2. Remove the HCO CR

1. oc delete hco kubevirt-hyperconverged -n openshift-cnv

3. After successful deletion of 'oc delete' command, create HCO CR ( "HyperConverged") from web-console ( Installed Operators -> create HyperConverged )

Actual results:
---------------
HCO CR never reaches stable condition