Implement ListVolumes

[andyzhangx]

Is your feature request related to a problem?/Why is this needed

When a Node gets deleted, and Pod is rescheduled, Kubernetes thinks that the the volume is still attached to the original node and fails to attach to the new node with Multi-Attach error.

Describe the solution you'd like in detail

The latest csi-attacher v2.1 adds support for the ListVolumes capability: https://github.com/kubernetes-csi/external-attacher/blob/v2.1.1/CHANGELOG-2.1.md

https://github.com/container-storage-interface/spec/blob/v1.3.0/spec.md#listvolumes
https://docs.microsoft.com/en-us/rest/api/compute/disks/listbyresourcegroup
https://github.com/kubernetes/kubernetes/blame/master/staging/src/k8s.io/legacy-cloud-providers/azure/clients/snapshotclient/azure_snapshotclient.go

It addresses problems when volumes may get detached out of band, and need to be reattached to a node. It could potentially help the other way around too, but that hasn't been tested.

depends on PR(#377)
Describe alternatives you've considered

Additional context

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.

[dr0pdb]

/assign