[cinder-csi-plugin] Allow setting parameters on chart-managed StorageClasses

[locker95]

What this PR does / why we need it:

The Helm chart's built-in csi-cinder-sc-delete / csi-cinder-sc-retain StorageClasses currently cannot carry any parameters (e.g. availability or type), forcing users to disable them and maintain custom classes just to set a parameter. This adds optional storageClass.delete.parameters and storageClass.retain.parameters values that are rendered into the respective StorageClass. They default to {}, and the rendered output is byte-identical to the previous chart when unset.

Which issue this PR fixes:

fixes #1980

Special notes for reviewers:

Picks up where the closed #2434 left off (thanks @sakshi-1505). Verified with helm template: output is unchanged with default values, and the parameters: block renders correctly when set; helm lint passes. Chart version bumped to 2.36.3, matching the patch-bump convention of recent chart changes (#3152, #3078). This PR was written in part with the assistance of generative AI.

Release note:

[cinder-csi-plugin] The Helm chart now supports setting `parameters` on the chart-managed delete/retain StorageClasses via `storageClass.<reclaim-policy>.parameters`.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign stephenfin for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

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

[kubernetes-prow]

Hi @locker95. Thanks for your PR.

I'm waiting for a kubernetes 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.

Details

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.