To Reproduce Steps to reproduce the behavior:

1. Renew the root CA certificate with `cmctl renew rootca-internal` - in T-O logs see that Autoscaling controller doesn't react to this. It only later reacts to memcached being changed because of this. Also see that aodh-0 pod didn't recreate.
2. Renew the internal aodh certificate with `cmctl renew aodh-internal-svc` - in T-O logs Autoscaling controller doesn't react at all. aodh-0 pod doesn't recreate even though it should.
3. Change the aodh password in osp-secret - Autoscaling doesn't react to this change at all, the Autoscaling controller should reconcile in the T-O logs and aodh-0 pod should recreate
4. Create a topology, configure it in oscp.telemetry.template.topologyRef, edit the topology - Autoscaling controller doesn't react to the change, aodh-0 pod doesn't get recreated.

Expected behavior

• Whenever a related secret is changed (e.g. tls certificate / key or the CA certificate), autoscaling controller is able to detect that change and restart the aodh pod if needed.

Additional context

• The configVars variable https://github.com/openstack-k8s-operators/telemetry-operator/blob/main/internal/controller/aodh_controller.go#L308 is usually being used to compute a hash and then based on that to restart pods when needed. This var is being assigned to, but it's not actually being used anywhere.
• Lot of the field paths here are just wrong https://github.com/openstack-k8s-operators/telemetry-operator/blob/main/internal/controller/autoscaling_controller.go#L223C1-L230C2
• The issue above is hidden by error reporting missing in https://github.com/openstack-k8s-operators/telemetry-operator/blob/main/internal/controller/autoscaling_controller.go#L984