operator: React to changes in ConfigMap used for storage CA

[xperimental]

What this PR does / why we need it:

The operator allows to set a custom CA used for accessing S3-based object storage using the spec.storage.tls.caName key. While the operator already produces an error when the ConfigMap referenced by that key does not exist or does not contain data, it does not automatically react to changes to the ConfigMap. This PR fixes that by watching for changes to ConfigMap resources.

Which issue(s) this PR fixes:

LOG-4897

Special notes for your reviewer:

• This commit of the PR contains a change to the predicate used for checking if a ConfigMap resource has changed. The old implementation used metadata.generation which is not used on ConfigMap resources. This PR changes this to use the metadata.resourceVersion instead which is available on all resources. The same code is also used for Service and Secret resource types.

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Tests updated
• CHANGELOG.md updated

[github-actions]

Trivy scan found the following vulnerabilities:

• HIGH, Target: docker.io/grafana/loki:main-3048e4a (alpine 3.18.4), Type: alpine openssl: Incorrect cipher key and IV length processing in libcrypto3 v3.1.3-r0. Fixed in v3.1.4-r0
• HIGH, Target: docker.io/grafana/loki:main-3048e4a (alpine 3.18.4), Type: alpine openssl: Incorrect cipher key and IV length processing in libssl3 v3.1.3-r0. Fixed in v3.1.4-r0
  \nTo see more details on these vulnerabilities, and how/where to fix them, please run docker build -t grafana/loki:main-3048e4a -f cmd/loki/Dockerfile .
  trivy i grafana/loki:main-3048e4a on your branch. If these were not introduced by your PR, please considering fixing them in via a subsequent PR. Thanks!