feat(csi): bump up csi provisioner to v3.5.0 and other updates

[vharsh]

Reason:

• v1 CSIStorageCapacity is GA since K8s 1.24 and in csi-provisioner 3.2.0 and above.
• In K8s 1.27 v1beta1/CSIStorageCapacity has been removed, so bumping this up will enable zfs-localpv to run on K8s 1.27 & above.

Pull Request template

Why is this PR required? What issue does it fix?:

• v1beta1/CSIStorageCapacity has been removed from Kubernetes 1.27 and v1/CSIStorageCapacity has been Generally Available since 1.24.

What this PR does?:

• bump up the versions of csi-provisioner to 3.5.0 from 3.0.0
• bump up other CSI sidecar versions
• bump up CI action specs
• update rbac permissions

Does this PR require any upgrade changes?:

• should not require specific upgrade changes

If the changes in this PR are manually verified, list down the scenarios covered::

• BDD tests seem to pass for this changeset

Any additional information for your reviewer? :

Checklist:

• Fixes Kubernetes 1.27 Deprecated CSIStorageCapacity: Storage.k8s.io/v1beta1: use v1. #437
• PR Title follows the convention of <type>(<scope>): <subject>
• Has the change log section been updated?
• Commit has unit tests
• Commit has integration tests
• (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
• (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

[avishnu]

Is the below PR description correct?
"bump up the versions of csi-provisioner to 3.2.0 from 3.5.0"

[avishnu]

Left a minor comment.
Lgtm

[vharsh]

"bump up the versions of csi-provisioner to 3.2.0 from 3.5.0"

No @avishnu, the csi-provisioner version has been bumped up to 3.5.0 in line with other bump ups in other storage engines. Anything over 3.2.0(inclusive) i.e. [3.2.0, latest] is good to use.

[Edit]: refer to commit --> feat(deploy): update CSI sidecars & snapshot CRDs to latest

[niladrih]

"bump up the versions of csi-provisioner to 3.2.0 from 3.5.0"

No @avishnu, the csi-provisioner version has been bumped up to 3.5.0 in line with other bump ups in other storage engines. Anything over 3.2.0(inclusive) i.e. [3.2.0, latest] is good to use.

[Edit]: refer to commit --> feat(deploy): update CSI sidecars & snapshot CRDs to latest

I edited the 3.2.0 from your PR comment to 3.0.0. I think it meant there was a commit updating the PR (which initially bumped provisioner to 3.2.0).

[avishnu]

"bump up the versions of csi-provisioner to 3.2.0 from 3.5.0"

No @avishnu, the csi-provisioner version has been bumped up to 3.5.0 in line with other bump ups in other storage engines. Anything over 3.2.0(inclusive) i.e. [3.2.0, latest] is good to use.
[Edit]: refer to commit --> feat(deploy): update CSI sidecars & snapshot CRDs to latest

I edited the 3.2.0 from your PR comment to 3.0.0. I think it meant there was a commit updating the PR (which initially bumped provisioner to 3.2.0).

I meant the linguistic bit. Should it be "from" 3.0.0 "to" 3.5.0?

[vharsh]

I meant the linguistic bit. Should it be "from" 3.0.0 "to" 3.5.0?

Right, the description is now updated by @niladrih

[vharsh]

Closing this as the changes have been cherry-picked in #461