Disable X_CSI_SPEC_DISABLE_LEN_CHECK for CSI controller

[chethanv28]

What this PR does / why we need it:

When customers create VCP volumes with long datastore names & with spbm policy, it is observed that volume names canend up with more than 128 characters. Now when customers move to CSI using the CSI migration feature, pod creation fails with the below error:
For ex: [Very-long-vsanDatastore-name] 4bb55260-de8a-c071-913b-020049bb8da4/kubernetes-dynamic-pvc-f8464f80-e90f-4356-ba4f-480fd47e7ea2.vmdk

rpc error: code = InvalidArgument desc = exceeds size limit: VolumeId: max=128, size=132

See https://github.com/kubernetes/kubernetes/issues/101153 for more details.
In vSphere CSI driver we can address this issue by disabling X_CSI_SPEC_DISABLE_LEN_CHECK ENV in the deployment yaml file.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:
Before:

  Warning  FailedAttachVolume  3s (x5 over 10s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-f8464f80-e90f-4356-ba4f-480fd47e7ea2" : rpc error: code = InvalidArgument desc = exceeds size limit: VolumeId: max=128, size=147

After:

  Normal  SuccessfulAttachVolume  0s         attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-f8464f80-e90f-4356-ba4f-480fd47e7ea2"

Release note:

[chethanv28]

jtest block-vanilla

[svcbot-qecnsdp]

Started Vanilla block pipeline...

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: testbed-deploy 

[chethanv28]

jtest block-vanilla

[svcbot-qecnsdp]

Started Vanilla block pipeline...

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: testbed-deploy 

[chethanv28]

jtest block-vanilla

[svcbot-qecnsdp]

Started Vanilla block pipeline...

[svcbot-qecnsdp]

Block vanilla build status: SUCCESS 
Stage before exit: finally 
Jenkins E2E Test Results: 

Ran 40 of 167 Specs in 8174.823 seconds
SUCCESS! -- 40 Passed | 0 Failed | 0 Pending | 127 Skipped
PASS

Ginkgo ran 1 suite in 2h18m25.482624268s
Test Suite Passed
make: Leaving directory `/home/worker/workspace/github-csi-block-vanilla/Results/475/vsphere-csi-driver`

[divyenpatel]

I see we are not updating - https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-7.0u2/vanilla

We will be removing the following directories, so if you can just update this in the 7.0u2 folder, it is fine.

https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-67u3
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-7.0/vanilla and
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-7.0u1/vanilla

[chethanv28]

I see we are not updating - https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-7.0u2/vanilla

We will be removing the following directories, so if you can just update this in the 7.0u2 folder, it is fine.

https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-67u3
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-7.0/vanilla and
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/master/manifests/dev/vsphere-7.0u1/vanilla

I have updated yaml in 70u2 folder. Also I am keeping the changes in 6.7u3, 7.0 and 7.0u1 since the PR to consolidate yamls will eventually remove the folder.

[divyenpatel]

approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chethanv28, divyenpatel

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 [chethanv28,divyenpatel]

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

[divyenpatel]

/lgtm