fix: respect ReadOnly AccessMode in volume mount

[andyzhangx]

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: respect ReadOnly AccessMode in volume mount

When user sets ReadOnlyMany or ReadOnlyOnce on the volume accessmode, the driver should append "ro" mount option during mount

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:

fix: respect ReadOnly AccessMode in volume mount

[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

[k8s-ci-robot]

@andyzhangx: 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-azurefile-csi-driver-e2e-capz-windows-2019	8cf84e8	link	true	/test pull-azurefile-csi-driver-e2e-capz-windows-2019
pull-azurefile-csi-driver-e2e-capz-windows-2019-hostprocess	8cf84e8	link	true	/test pull-azurefile-csi-driver-e2e-capz-windows-2019-hostprocess
pull-azurefile-csi-driver-e2e-migration-windows	8cf84e8	link	true	/test pull-azurefile-csi-driver-e2e-migration-windows
pull-azurefile-csi-driver-e2e-capz-windows-2022-hostprocess	8cf84e8	link	true	/test pull-azurefile-csi-driver-e2e-capz-windows-2022-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.

[andyzhangx]

/retest

[andyzhangx]

/cherrypick release-1.24

[andyzhangx]

/cherrypick release-1.30

[k8s-infra-cherrypick-robot]

@andyzhangx: #2031 failed to apply on top of branch "release-1.24":

Applying: fix: respect ReadOnly AccessMode in volume mount
Using index info to reconstruct a base tree...
M	pkg/azurefile/nodeserver.go
M	pkg/azurefile/utils.go
M	pkg/azurefile/utils_test.go
M	test/e2e/dynamic_provisioning_test.go
M	test/e2e/testsuites/specs.go
M	test/e2e/testsuites/testsuites.go
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/testsuites/testsuites.go
CONFLICT (content): Merge conflict in test/e2e/testsuites/testsuites.go
Auto-merging test/e2e/testsuites/specs.go
CONFLICT (content): Merge conflict in test/e2e/testsuites/specs.go
Auto-merging test/e2e/dynamic_provisioning_test.go
CONFLICT (content): Merge conflict in test/e2e/dynamic_provisioning_test.go
Auto-merging pkg/azurefile/utils_test.go
Auto-merging pkg/azurefile/utils.go
Auto-merging pkg/azurefile/nodeserver.go
CONFLICT (content): Merge conflict in pkg/azurefile/nodeserver.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 fix: respect ReadOnly AccessMode in volume mount
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-1.24

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.

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #2032

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.