Silence sliding window cluster correction config

Possibly a non-issue for offline, but in trigger jobs we see many repeated INFO messages of the following sort:

Py:CaloClusterCorrection    INFO EM sliding-window corrections for ele35 (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for ele55 (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for ele37 (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for gam35_unconv (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for gam55_unconv (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for gam37_unconv (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for gam35_conv (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for gam55_conv (EGSuperCluster) using version v12phiflip_supercluster
Py:CaloClusterCorrection    INFO EM sliding-window corrections for gam37_conv (EGSuperCluster) using version v12phiflip_supercluster

They are repeated every time this config is invoked, which is once per egamma trigger reconstruction variant.

I would have preferred to cache the configuration such that it is invoked only once, but this would require a sizeable change to convert a lot of lists into tuples before they are passed to the function here, in many files, so simply moving the message to DEBUG level.

@kristin @ahabouel FYI. As there have been no substantial changes other than code quality in several years, I assume there is not that much value in being able to see these messages in every job.