[Hyper-V] Use I/O scheduler noop/none for better disk I/O performance

**What are you trying to do?**
When running on Hyper-V, the recommendation is to _[pass] the scheduling decisions to the underlying Hyper-V hypervisor_: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/best-practices-for-running-linux-on-hyper-v#use-io-scheduler-noopnone-for-better-disk-io-performance.

We'd still better measure first, considering 2 cases:

- Hyper-V on bare metal
- Hyper-V running nested on KVM

Users should be able to do this manually too, so not the highest priority.

Start by measuring I/O scheduler behavior in the two environments named in the issue: Hyper-V on bare metal and Hyper-V nested on KVM. Then inspect the existing Hyper-V handling and scheduler configuration paths. Done should include evidence from both cases and a clear way for users to apply the scheduler choice manually or automatically.

Written by the indexing model from the issue text.