Add NodeStageVolume disk size validation before mounting

[hajiler]

What type of PR is this?

/kind bug

What this PR does / why we need it:
This PR introduces a safeguard to compare a disk's reported size against its expected size before running mkfs. If the disk's actual size does not match the expected size, the NodeStageVolume fails, and the operation will be retried.

Which issue(s) this PR fixes:

Fixes #
#2179

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Introduced a safeguard in NodeStageVolume to compare a disk's reported size against its expected size before running mkfs. If the sizes do not match, the operation will fail and be retried.

Note: To enable this validation, the --enable-disk-size-validation flag must be set to true on the node server.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hajiler
Once this PR has been reviewed and has the lgtm label, please assign amacaskill for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[hajiler]

/retest

[hajiler]

/retest

[hajiler]

/retest

[k8s-ci-robot]

@hajiler: The following tests 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-gcp-compute-persistent-disk-csi-driver-e2e-windows-2022	a6bd669	link	false	/test pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-2022
pull-gcp-compute-persistent-disk-csi-driver-e2e-arm	a6bd669	link	false	/test pull-gcp-compute-persistent-disk-csi-driver-e2e-arm
pull-gcp-compute-persistent-disk-csi-driver-verify	a6bd669	link	true	/test pull-gcp-compute-persistent-disk-csi-driver-verify

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.

[mattcary]

The govet error must be a new check, as that setup_e2e_test code has been in since february.

I'll force-submit, and push a PR to fix the e2e test.

[hajiler]

/cherry-pick release-1.21

[k8s-infra-cherrypick-robot]

@hajiler: #2178 failed to apply on top of branch "release-1.21":

Applying: Add NodeStageVolume disk size validation before mounting
Using index info to reconstruct a base tree...
M	pkg/gce-pd-csi-driver/node.go
M	pkg/gce-pd-csi-driver/node_test.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/gce-pd-csi-driver/node_test.go
Auto-merging pkg/gce-pd-csi-driver/node.go
Applying: Flag protect disk validation
Using index info to reconstruct a base tree...
M	cmd/gce-pd-csi-driver/main.go
M	pkg/gce-pd-csi-driver/gce-pd-driver.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/gce-pd-csi-driver/gce-pd-driver.go
Auto-merging cmd/gce-pd-csi-driver/main.go
CONFLICT (content): Merge conflict in cmd/gce-pd-csi-driver/main.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 0002 Flag protect disk validation

In response to this:

/cherry-pick release-1.21

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.