Restrict auto-config changes to relevant changes by exclusion of section from configSHA annotation

Currently, the helm charts generate a SHA based on the whole ConfigMap change and use this SHA as an annotation in the Deployment.
This means whenever there's any change in the ConfigMap (e.g. via helm update ..), the affected pod(s) auto-restart.

Parts of the ConfigMap generated for each component isn't used, in other words, even if it changes, it will have no effect on the functionality of the component.
To avoid needless pod restarts on updates, selectively filter sections and properties from the config SHA, so that it doesn't change, and cause a restart unnecessarily.