Avoid getting the trusted certificates Secrets twice -> once for the certs and once for hash #11972
Description
Right now we seem to get the trusted certificate Secrets twice when reconciling Kafka Connect and MM2:
- We first get them to get the certificates and copy them into our own Secret
- Next we get them again to calculate the hash of the trusted certificates, authentication credentials, etc.
This seems like a waste of resources and we should try to improve this. It seems to be left over from the time when the trusted certificates were mounted and we were getting them only once for the authentication hash (to reload the Pods when the certificates change).
However, it is slightly complicated by the copying of the trusted certs being done only for Connect and partially for MM2. It is not done for MM2 connectors and for Bridge. So we need to synchronize this.