changes to support hyperdisk multi-writer mode

[karkunpavan]

What type of PR is this?
/kind bug

What this PR does / why we need it:
Hyper disk multi-writer support is now in compute/v1 but the persistent disk csi driver still calls v0.beta which leads a error while creating a hyperdisk with multi-writer mode.

Error:

Warning ProvisioningFailed 31m (x15 over 57m) pd.csi.storage.gke.io_wduan-1030a-g-vdnqh-master-0_dc46e9f6-1725-4f15-922c-99f0e281e102 failed to provision volume with StorageClass
"balanced-storage": rpc error: code = InvalidArgument desc = CreateVolume failed: rpc error: code = InvalidArgument desc = CreateVolume failed to create single zonal disk pvc-0b65d680-636b-46c6-876d-d3a6c412c3ef: failed to insert zonal disk: unknown Insert disk error:
googleapi: Error 400: Invalid value for field 'resource.multiWriter': 'true'.
Cannot specify the multi writer field for 'hyperdisk-balanced' disks,
please use access mode instead., invalid%!v(MISSING)

To fix this here are the changes done:

1. Add AccessMode param to DiskParameters struct
2. Initialize the AccessMode field to default value in ExtractAndDefaultParameters()
3. The parameter is read by controller in createVolumeInternal()
4. The accessMode before calling createSingleZoneDisk() and createRegionalDisk() is currently set to "", the change fixes createsingledisk() to read from the parameter passed by the user.
5. insertZonalDisk() currently calls beta APIs when multi-writer is set, the fix is to use v1 API instead.
6. insertRegionalDisk() currently calls beta APIs when multi-writer is set, the fix is to use v1 API instead.
7. Enable the multiwriter e2e tests to test creation and lifecycle of multi-writer disks.
8. Delete stale comments about hyperdisk and multi-writer support

Which issue(s) this PR fixes:

Fixes #1863

Special notes for your reviewer:

• This issue and the fix proposal has been discussed with Matthew and Hung

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: karkunpavan
Once this PR has been reviewed and has the lgtm label, please assign msau42 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

[k8s-ci-robot]

Hi @karkunpavan. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: karkunpavan / name: Pavan Karkun (5789a07, 16433ea)
• ✅ login: sjswerdlow (6d5f693, c85f509, 615b44f, c06aea7)

[mattcary]

/ok-to-test