test(e2e): add vm version test using new framework

[hardcoretime]

Description

Migrating e2e test VirtualMachineVersions from legacy approach to the new framework.

The test verifies that qemu and libvirt versions are present in the VirtualMachine status.

Technical changes:

• Uses framework.NewFramework() instead of kustomize + kubectl
• Resources are created programmatically via builders (vdbuilder, vmbuilder)
• State waiting via util.UntilObjectPhase() instead of WaitPhaseByLabel
• Automatic cleanup via CreateWithDeferredDeletion()

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

According to the roadmap, all legacy e2e tests need to be gradually migrated to the new framework. This simplifies test code, makes them more declarative, and faster by using direct API calls instead of kubectl.

What is the expected result?

The VirtualMachineVersions test passes successfully and verifies that qemu and libvirt versions are present in VM status.

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.

Changelog entries

section: test
type: chore
summary: "Migrate e2e test VirtualMachineVersions to new framework."
impact_level: low