Make separate CNS creation and deletion maps for VCs during full Sync

[skogta]

What this PR does / why we need it:
cnsCreationMap and cnsDeletion maps are being shared across all VCs which is causing clean up of volumes from these maps. To fix this, these maps will become map of map where each VC will have its separate map of volumes to be deleted and created.

Testing done:
Tested for vanilla (FSS enabled as well as disabled) and SV cluster:

1. Create a PV via CSI and then delete the coressponsing CNS volume from VC.
2. Observed that CNSCreationMap got populated.
3. In the next full sync cycle, the CNS volume re-appreaed on VC UI.

Tested for vanilla (FSS enabled as well as disabled) and SV cluster:

1. Created CNS volume on VC.
2. Observed that CNSDeletionMap got populated.
3. In the next full sync cycle, the CNS volume got deleted - confirmed the same from UI.

Special notes for your reviewer:

Release note:

[k8s-ci-robot]

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

[akankshapanse]

/ok-to-test

[k8s-ci-robot]

@akankshapanse: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

[akankshapanse]

/approve

[divyenpatel]

/ok-to-test

[divyenpatel]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akankshapanse, divyenpatel, skogta

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

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