Support configuring updateStrategy.rollingUpdate.maxUnavailable in Helm charts

[chrisamert]

Describe the solution you'd like
Right now the Helm Chart configure the Daemonset with the RollingUpdate strategy, but don't provide any option so specify the 'maxUnavailble' property, so the default value of '1' is being used. On our 60+ node clusters this is causing the deployment to take 40+ minutes to complete. It would be great if the Helm charts allowed 'maxUnavailable' to be configurable so more than one node can be updated at once.

Anything else you would like to add:
Related issue in the KeyVault Provider repo: Azure/secrets-store-csi-driver-provider-azure#283

Environment:

• Secrets Store CSI Driver version: (use the image tag):
• Kubernetes version: (use kubectl version):

[aramase]

/assign @chrisamert