Description of problem:

The details section of a VirtualMachine using instance types and preferences links to the resources associated with the VirtualMachine:

However on the backend we are capturing copies of these resources as ControllerRevisions and associating these with the VirtualMachine:

The UI should really link to these ControllerRevisions and optionally disable the version of the instance type or preference held within. Otherwise users could become easily confused if the original instance type or preferences are mutated and no longer match what is being used by their VirtualMachine.

https://kubevirt.io/user-guide/virtual_machines/instancetypes/#versioning

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

v4.15

How reproducible:

Always

Steps to Reproduce:

1. Create a VirtuialMachine using an instance type and preference through the UI
2. Review the details of the VirtualMachine post creation
3.

Actual results:

The original instance type and preference are linked from the details page

Expected results:

The copies of the original instance type and preference held within the associated ControllerRevisions are linked from the details page

Additional info: