fix external e2e test failures

[andyzhangx]

What happened:

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_azuredisk-csi-driver/2468/pull-azuredisk-csi-driver-external-e2e-single-az/1824285579567697920

�[38;5;9m�[1mSummarizing 3 Failures:�[0m
  �[38;5;9m[FAIL]�[0m �[0mExternal Storage [Driver: test.csi.azure.com] �[38;5;243m[Testpattern: Dynamic PV (default fs)] provisioning �[38;5;9m�[1m[It] should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]�[0m
  �[38;5;243mtest/e2e/framework/volume/fixtures.go:584�[0m
  �[38;5;9m[FAIL]�[0m �[0mExternal Storage [Driver: test.csi.azure.com] �[38;5;9m�[1m[Testpattern: Dynamic PV (block volmode)] volumeMode [DeferCleanup (Each)] �[0mshould fail to use a volume in a pod with mismatched mode [Slow]�[0m
  �[38;5;243mtest/e2e/storage/testsuites/volumemode.go:190�[0m
  �[38;5;9m[FAIL]�[0m �[0mExternal Storage [Driver: test.csi.azure.com] �[38;5;243m[Testpattern: Dynamic PV (default fs)] read-write-once-pod �[38;5;9m�[1m[It] should preempt lower priority pods using ReadWriteOncePod volumes�[0m
  �[38;5;243mtest/e2e/storage/testsuites/readwriteoncepod.go:156�[0m

�[38;5;9m�[1mRan 94 of 7486 Specs in 1090.400 seconds�[0m
�[38;5;9m�[1mFAIL!�[0m -- �[38;5;10m�[1m91 Passed�[0m | �[38;5;9m�[1m3 Failed�[0m | �[38;5;11m�[1m0 Pending�[0m | �[38;5;14m�[1m7392 Skipped�[0m

What you expected to happen:

How to reproduce it:

Anything else we need to know?:

Environment:

• CSI Driver version:
• Kubernetes version (use kubectl version):
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten