Fix virtio-win install steps for EL hosts (#657)

* Fix virtio-win install steps for EL hosts

* Clarify VDDK download and version guidance

* Clarify VDDK 8 recommendation for VMware imports

* Update instructions for importing VMware VMs into KVM

Clarify installation instructions for virt-v2v and virtio drivers, including logging and error handling for Windows VMs.

* Revise VMware to KVM import instructions

Updated the instructions for importing VMware VMs into KVM, including recommendations for virt-v2v versions and installation steps for required tools.

* Warn about outdated distro virtio-win packages and the Windows Server 2025 smbus driver issue

The Enterprise Linux distribution virtio-win packages can be old enough
to contain no drivers for recent Windows releases, in which case
virt-v2v converts the guest without a virtio storage driver and the
imported VM cannot boot. Document overwriting the ISO with the latest
upstream build, and document the Windows Server 2025 first-boot reboot
loop caused by the rejected smbus driver signature, with its
workaround.

* Give exact commands for removing the smbus driver from the virtio-win ISO

The previous note said to remove the driver from the driver set without
explaining that virt-v2v reads it from the ISO itself, which cannot be
edited in place. Document the full extract, delete and rebuild sequence
with xorriso; verified on an EL9 conversion host against virtio-win
0.1.285.

* Strongly recommend setting vddk.lib.dir explicitly instead of relying on auto-detection

Auto-detection of the VDDK directory can pick up the wrong libraries on
real hosts - leftovers from container images, a second VDDK
installation, or a partially extracted tree - and the resulting
conversion failures are hard to trace to the wrong library path. The
text presented the property as an option for non-standard locations;
it is now the recommended default, with auto-detection described as a
fallback only. This also completes a sentence that was previously cut
off mid-reference.

* Clarify that the smbus ISO rebuild is needed for Windows Server 2025 and newer only

Older Windows releases accept the driver's signature and work with the
unmodified upstream ISO; make that explicit so operators do not rebuild
the ISO unnecessarily.

---------

Co-authored-by: Codex <codex@openai.com>