fix: support disk discovery on Windows Gen2 and v6 VM sku

[andyzhangx]

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: support disk discovery on Windows Gen2 and v6 VM sku

Windows team provided the following info:

• normal scsi data disk
  "Model": "Microsoft Virtual Disk"
• v6 nvme controller data disk
  "Model": "Virtual_Disk NVME Premium"

thus I think we could use this filter: ConvertTo-Json @(Get-CimInstance win32_diskdrive | Where-Object { $_.Model -eq "Virtual_Disk NVME Premium" -or $_.SCSIPort -Ne 0 } | Select-Object Index, SCSILogicalUnit, SCSITargetId, SCSIPort, SCSIBus, Model), thus we could fix this issue permanently.

 - scsi data disk
PS C:\> ConvertTo-Json @(Get-CimInstance win32_diskdrive | Where-Object { $_.Model -like "*Virtual?Disk*" } | Select-Object Index, SCSILogicalUnit, SCSITargetId, SCSIPort, SCSIBus, Model)
[
    {
        "Index":  2,
        "SCSILogicalUnit":  0,
        "SCSITargetId":  0,
        "SCSIPort":  3,
        "SCSIBus":  0,
        "Model":  "Microsoft Virtual Disk"
    },
    {
        "Index":  3,
        "SCSILogicalUnit":  1,
        "SCSITargetId":  0,
        "SCSIPort":  3,
        "SCSIBus":  0,
        "Model":  "Microsoft Virtual Disk"
    },
    {
        "Index":  4,
        "SCSILogicalUnit":  2,
        "SCSITargetId":  0,
        "SCSIPort":  3,
        "SCSIBus":  0,
        "Model":  "Microsoft Virtual Disk"
    },
    {
        "Index":  5,
        "SCSILogicalUnit":  3,
        "SCSITargetId":  0,
        "SCSIPort":  3,
        "SCSIBus":  0,
        "Model":  "Microsoft Virtual Disk"
    }
]

- v6 nvme controller data disk
PS C:\hpc> ConvertTo-Json @(Get-CimInstance win32_diskdrive | Where-Object { $_.Model -like "*Virtual?Disk*" } | Select-Object Index, SCSILogicalUnit, SCSITargetId, SCSIPort, SCSIBus, Model)
[
    {
        "Index":  0,
        "SCSILogicalUnit":  0,
        "SCSITargetId":  0,
        "SCSIPort":  0,
        "SCSIBus":  0,
        "Model":  "Virtual_Disk NVME Premium"
    },
    {
        "Index":  2,
        "SCSILogicalUnit":  1,
        "SCSITargetId":  0,
        "SCSIPort":  0,
        "SCSIBus":  0,
        "Model":  "Virtual_Disk NVMe Premium"
    },
    {
        "Index":  3,
        "SCSILogicalUnit":  2,
        "SCSITargetId":  0,
        "SCSIPort":  0,
        "SCSIBus":  0,
        "Model":  "Virtual_Disk NVMe Premium"
    },
    {
        "Index":  4,
        "SCSILogicalUnit":  3,
        "SCSITargetId":  0,
        "SCSIPort":  0,
        "SCSIBus":  0,
        "Model":  "Virtual_Disk NVMe Premium"
    },
    {
        "Index":  5,
        "SCSILogicalUnit":  4,
        "SCSITargetId":  0,
        "SCSIPort":  0,
        "SCSIBus":  0,
        "Model":  "Virtual_Disk NVMe Premium"
    }
]

Which issue(s) this PR fixes:

Fixes #2365, #2661

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

fix: support disk discovery on Windows Gen2 and v6 VM sku

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[andyzhangx]

/retest

[andyzhangx]

/retest

[andyzhangx]

/retest

[andyzhangx]

/retest

[andyzhangx]

/retest

[k8s-ci-robot]

@andyzhangx: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-azuredisk-csi-driver-e2e-capz-windows-2019-hostprocess	7c070fe	link	true	/test pull-azuredisk-csi-driver-e2e-capz-windows-2019-hostprocess

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.