Validate the full feature set with Hyper-V enabled

[btsouth]

Run the normal launch, GPU fallback, clipboard, folder sharing, audio, reboot, and shutdown checks on a Windows machine with the full Hyper-V feature set enabled. Update the FAQ with the result.

[btsouth]

Partial result, plus a harness note for whoever picks this up.

Windows 10 22H2 was tested on real hardware (ASUS ROG, 32 GB) and reported working well. That covers the normal launch path on Win10.

The harness note: this cannot be validated in a dockur/KVM Windows 10 VM. Once the launcher enables HypervisorPlatform, every boot with VMX exposed hangs in a spin loop in winload. Ruled out hv_passthrough as shipped, CPU_FLAGS=-hv-evmcs, and HV=N. dockur itself defaults VMX=N for Windows guests for the same reason. The VM has to run VMX=N, which boots fine but leaves WHPX unavailable, so nothing that needs to boot an Omarchy guest can run there.

The Windows 11 VM does run nested WHPX, so it is the one to use for anything that has to actually boot Omarchy. Real hardware is still needed for the full Hyper-V matrix.