refactor(core): more renames to not overlap with original Kubevirt and CDI

[diafour]

Description

• Rewrite app.kubernetes.io/managed-by labels value
• Rewrite names for validatingwebhooks, mutatingwebhooks in Kubevirt.
• Add deduplication and anti-shadowing algorithms: delete original resources from discovery and CRD list, prefix original labels on restore, un-prefix on rename.
• Rename devices on nodes and change device plugin socket path, so virt-handlers can live together.
• Remove upload.cdi.kubevirt.io ApiService.

Why do we need it, and what problem does it solve?

DVP can work together with original CDI and KubeVirt in the same cluster.

What is the expected result?

Working scenarios:

Install original cdi+kubevirt along with DVP

1. Ensure DVP is installed
2. Install CDI and KubeVirt, enable LiveMigration in Kubevirt CR.
3. Launch VM in DVP and in original KubeVirt. Ensure PVCs are created and both VMs are in the Running state.
4. Migrate both VMs. Ensure both are migrated.
5. Uninstall KubeVirt and CDI.
6. Ensure no cluster resources are left from original CDI and Kubevirt.
7. Ensure no errors in logs in DVP components.

Install DVP along with original cdi+kubevirt

1. Ensure original CDI and KubeVirt are installed.
2. Enable DVP module.
3. Launch VM in DVP and in original KubeVirt. Ensure PVCs are created and both VMs are in the Running state.
4. Migrate both VMs. Ensure both are migrated.
5. Disable DVP module. Ensure deckhouse queue is empty, no d8-virtualization namespace.
6. Ensure no cluster resources are left from DVP (NodeGroupConfiguration, ClusterRole, internalvirtualization* CRDs etc.). Only 2 CRDs should remain: internalvirtualizationkubevirts and internalvirtualizationcdis.
7. Ensure no errors in logs in original KubeVirt and CDI.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.