Updating acl secret does not update ACL LIST

If the secret which is used for the ACL (via aclFromSecret) is updated then the `ACL LIST` remains the same until `ACL LOAD` is called.

There's no way of knowing outside of the pod when the secret has been propagated to within the pod so `ACL LOAD` does not do anything if called at the wrong time. Additionally, if you have multiple replicas then calling `ACL LOAD` won't do anything for the replicas.

Is there a way of adding an option such that if the acl config file is updated then the pod automatically calls `ACL LOAD`?

Trace how aclFromSecret is handled in the operator and how Kubernetes Secret updates reach managed pods. Check the behavior around ACL LOAD, including multiple replicas, and identify the existing reconciliation or watch entry point. Done means an ACL configuration update reliably causes every replica to load the new ACL without manual intervention.

Written by the indexing model from the issue text.