fix: resize is required after snapshot restore/volume clone on Windows

[andyzhangx]

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: resize is required after snapshot restore/volume clone on Windows

we use Get-Volume -UniqueId \"$Env:volumeID\" | Get-partition | Get-PartitionSupportedSize | Select SizeMax
to get the targetVolumeSize, and we use following command to get the currentVolumeSize

(Get-Volume -UniqueId \"$Env:volumeID\\" | Get-partition).Size

if targetVolumeSize > currentVolumeSize, then we should resize.

But as following example, you could see for a 29.98 GB disk, just right after it's formatted, targetVolumeSize is always bigger than currentVolumeSize (just 1MB bigger), so resize operation would always happen. I think this is a bug, only if targetVolumeSize > currentVolumeSize + 1GB, then we should perform resize operation, in that case, NodeStageVolume should succeed.

(Get-Disk -Number 3 | Get-Partition | Get-Volume).UniqueId
PS C:\> Get-Volume -UniqueId "\\?\Volume{ccfda246-2790-4cf3-9fbf-37a62e1f9f6d}\" | Get-partition
   DiskPath: \\?\scsi#disk&ven_msft&prod_virtual_disk#6&23db5f40&0&000001#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

PartitionNumber  DriveLetter Offset                                                           Size Type
---------------  ----------- ------                                                           ---- ----
2                G           16777216                                                     29.98 GB Basic

PS C:\> (Get-Volume -UniqueId "\\?\Volume{ccfda246-2790-4cf3-9fbf-37a62e1f9f6d}\" | Get-partition).Size
32194428928
PS C:\> Get-Volume -UniqueId "\\?\Volume{ccfda246-2790-4cf3-9fbf-37a62e1f9f6d}\" | Get-partition | Get-PartitionSupportedSize | Select SizeMax

    SizeMax
    -------
32195460608

Which issue(s) this PR fixes:

Fixes #

Requirements:

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

Special notes for your reviewer:

Release note:

none

[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]

/cherrypick release-1.31

[k8s-infra-cherrypick-robot]

@andyzhangx: #2733 failed to apply on top of branch "release-1.31":

Applying: fix: resize is required after snapshot restore/volume clone on Windows
Using index info to reconstruct a base tree...
M	pkg/os/volume/volume.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/os/volume/volume.go
CONFLICT (content): Merge conflict in pkg/os/volume/volume.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 fix: resize is required after snapshot restore/volume clone on Windows

In response to this:

/cherrypick release-1.31

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.

[andyzhangx]

/cherrypick release-1.31

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #2734

In response to this:

/cherrypick release-1.31

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.

[andyzhangx]

/cherrypick release-1.30

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #2754

In response to this:

/cherrypick release-1.30

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.