1. Proposed title of this feature request
HCP KubeVirt Nodepool CR support for additional disks

2. What is the nature and description of the request?
Some (software defined) storage solutions, especially when accessed via Fibre Channel, do require raw devices to be available inside of a `hostedCluster` worker nodes. As of today there is no supported path to attach additional disks to the `NodePools`. The kubevirt hypershift.openshift.io/kubevirt-vm-jsonpatch annotation is available for NodePools

$ oc annotate -n clusters nodepool ${NODEPOOL_NAME} \                             
'hypershift.openshift.io/kubevirt-vm-jsonpatch=[{"op": "add","path": "/spec/template/spec/domain/devices/disks/-","value": {"name": "additional-disk","disk": {"bus": "virtio"}}},{"op": "add","path": "/spec/template/spec/volumes/-","value": {"name": "additional-disk","emptyDisk": {"capacity": "2Gi"}}}]' 

but specifically unsupported as explained in https://issues.redhat.com/browse/CNV-23418. Modifying the `VirtualMachine` objects would be a workaround which does not align with Infrastructure-as-code / GitOps practices, as only the `NodePool` and `HostedCluster` CR would be available in git.  
Need a supported solution to attach `virtio` and `scsi` devices via the `NodePool` CR to the `VirtualMachines` of the `HostedCluster.

3. Why does the customer need this? (List the business requirements here)

• Need usable raw devices inside of the `HostedCluster` worker nodes for (software defined) storage solution, e.g. Portworx Enterprise
• Need to not lose Infrastructure-as-code capability when provisioning storage inside of the `HostedCluster`
• Need to use a storage inside of the `HostedCluster` which does not depend on kubevirt-csi due to tenant isolation

4. List any affected packages or components.