Add check for CSI volume spec in PVUpdated method

[chethanv28]

What this PR does / why we need it:
This PR is adding CSI check for volume spec in metadatasyncer. Currently we are assuming that the volumes are always CSI volumes, however for migrated volumes the spec does not contain CSI field and hence a crash was observed during CSI migration testing.

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

Testing done:
Before:

1. Create in-tree volumes
2. Deploy CSI driver
3. Enable CSI migration FSS
4. Enable Migration flags on kube-controller-manager and kubelet

k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
	/go/pkg/mod/k8s.io/apimachinery@v0.21.1/pkg/util/runtime/runtime.go:55 +0x109
panic(0x203bdc0, 0x385fbb0)
	/usr/local/go/src/runtime/panic.go:965 +0x1b9
sigs.k8s.io/vsphere-csi-driver/pkg/syncer.csiPVUpdated(0x27e8c78, 0xc0010a8090, 0xc0008ff900, 0xc00024b900, 0xc0000ec000)
	/build/pkg/syncer/metadatasyncer.go:989 +0x304

Performed same steps after the fix and no crash was observed

&
Running e2e pipelines

Special notes for your reviewer:

Release note:

Add check for volume spec in PVUpdated

[svcbot-qecnsdp]

Started Vanilla block pre-checkin pipeline... Build Number: 105

[chethanv28]

This change needs to be cherry-picked to 2.3 & 2.2.
cc @divyenpatel Can you help add labels for the same

[gohilankit]

Change looks good to me.
/approve

[svcbot-qecnsdp]

Build ID: 105
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 45 of 195 Specs in 11417.785 seconds
FAIL! -- 44 Passed | 1 Failed | 0 Pending | 150 Skipped
--- FAIL: TestE2E (11417.87s)
FAIL

Ginkgo ran 1 suite in 3h10m57.042729493s
Test Suite Failed
make: Leaving directory `/home/worker/workspace/csi-block-vanilla-pre-check-in/105/vsphere-csi-driver`

[chethanv28]

Build ID: 105
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 45 of 195 Specs in 11417.785 seconds
FAIL! -- 44 Passed | 1 Failed | 0 Pending | 150 Skipped
--- FAIL: TestE2E (11417.87s)
FAIL

Ginkgo ran 1 suite in 3h10m57.042729493s
Test Suite Failed
make: Leaving directory `/home/worker/workspace/csi-block-vanilla-pre-check-in/105/vsphere-csi-driver`

[csi-block-vanilla] [csi-supervisor] statefulset
/home/worker/workspace/csi-block-vanilla-pre-check-in/105/vsphere-csi-driver/tests/e2e/statefulsets.go:56
  Statefulset testing with parallel podManagementPolicy [It]
  /home/worker/workspace/csi-block-vanilla-pre-check-in/105/vsphere-csi-driver/tests/e2e/statefulsets.go:266

  Unexpected error:
      <*errors.StatusError | 0xc0004dec80>: {
          ErrStatus: {
              TypeMeta: {Kind: "", APIVersion: ""},
              ListMeta: {
                  SelfLink: "",
                  ResourceVersion: "",
                  Continue: "",
                  RemainingItemCount: nil,
              },
              Status: "Failure",
              Message: "etcdserver: request timed out",
              Reason: "",
              Details: nil,
              Code: 500,
          },
      }
      etcdserver: request timed out
  occurred

The 1 failure is a known intermittent failure which is tracked internally.

cc: @divyenpatel
Can you help with approvals & merge the PR

[divyenpatel]

/approve
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

[svcbot-qecnsdp]

Build ID: 24
WCP build status: FAILURE 
Stage before exit: null 

[svcbot-qecnsdp]

Build ID: 25
WCP build status: FAILURE 
Stage before exit: null