Add checksum annotation for secrets rendering

[mrballcb]

Is this a new chart

NO

What this PR does / why we need it:

Adds a "checksum/secrets" checksum annotation to the deployment.

We do daily scheduled deployments to refresh short lived AWS keys. The helm
chart stores AWS keys as kube secrets. When nothing else changes but the AWS keys,
the deployment is not perceived as changed, no new replicaset gets created, and no
pod restart occurs.

Which issue this PR fixes

• fixes stable/prometheus-cloudwatch-exporter Add secrets checksum to deployment annotations #22448

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• DCO signed
• Title of the PR starts with chart name (e.g. [stable/mychartname])

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mrballcb
To complete the pull request process, please assign torstenwalter
You can assign the PR to them by writing /assign @torstenwalter in a comment when ready.

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

Needs approval from an approver in each of these files:

• stable/prometheus-cloudwatch-exporter/OWNERS

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

[k8s-ci-robot]

Hi @mrballcb. Thanks for your PR.

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

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.