[helm] Avoid unnecessary pod restart on each helm chart version

[jkroepke]

What this PR does / why we need it:

Currenty, loki restarts on each new helm chart version. The reason here is that the whole Kubernetes secrets is used to generated the config checksum. The Kubernetes secrets contains labels, which contains the helm chart version. A new version would change the checksum, too.

From my point of view, a restart is only necessary, if PodSpec or config has been changed.

This isn't necessary.

Ref:

• [grafana] Avoid unnecessary pod restart on each helm chart version helm-charts#2834
• [promtail] Avoid unnecessary pod restart on each helm chart version helm-charts#2833

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• CHANGELOG.md updated
  • If the change is worth mentioning in the release notes, add add-to-release-notes label
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

[JStickler]

@jkroepke Could you please complete these items on the PR checklist? For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md.

[jkroepke]

Done. Sorry, I miss files to commit on my machine

[jkroepke]

Conflicts resolved.

[jkroepke]

I did a merge from main here. I would appreciate a review soon.