Description of problem:
When running on an AMD system, if a Windows VM is created using:
hyperv:
evmcs:
enabled: false

scheduling will fail due to:
Node-Selectors: cpu-feature.node.kubevirt.io/vmx=true
cpu-vendor.node.kubevirt.io/Intel=true

Version-Release number of selected component (if applicable):
4.11.0

How reproducible:
Every time

Steps to Reproduce:
1. Create a VM w/ evmcs explicitly set to false, selected to run on an AMD node
2. oc describe virt-launcher pod to see scheduling failure (node(s) didn't match Pod's node affinity/selector)

Actual results:
Virt-launcher pod cannot be scheduled.

Expected results:
If the feature is explicitly disabled, it should not prevent scheduling.