Description of problem:
Currently if a node has host-model cpu that is included in ObsoleteCPUModels
and we create vmi with host-model cpu it can still be scheduled to that node,
than the vmi will run with host-model cpu and won't be able to migrate.

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

How reproducible:
Add a node's host-model cpu model to the ObsoleteCPUModels
can find out which model is that through the node's label:
"host-model-cpu.node.kubevirt.io/<HostModelOfTheNode>": "true"

Create a vm to start on the node with host-model(the default cpuModel)

Actual results:
The vm will be scheduled and run with the obsolete cpuModel

Expected results:
Virt launcher shouldn't be scheduled

Additional info: