feat(chart): expose automountServiceAccountToken in the csi-driver chart

[yugstar]

What

Adds an automountServiceAccountToken value to the csi-driver chart so operators can disable automatic mounting of the ServiceAccount token on the csi-driver pod — a common security-hardening request, matching the option already in the trust-manager chart.

Details

• New automountServiceAccountToken value (defaults to true, preserving current behaviour).
• Rendered on the DaemonSet pod spec via {{- if hasKey .Values "automountServiceAccountToken" }}.
• Regenerated values.schema.json and README.md with helm-tool.

helm lint passes; helm template --set automountServiceAccountToken=false renders the field correctly.

[cert-manager-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 hjoshi123 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

[cert-manager-prow]

Hi @yugstar. Thanks for your PR.

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