Version of components:

tempo-operator.v0.12.0-2

Description of the problem:

If a TempoStack is created and then deleted after sometime, the alert TempoStackUnhealthy will be firing for the deleted instance. 

Steps to reproduce the issue:
*Install the latest Tempo and OTEL operator from the latest RHOSDT 3.3 build.

*Create a TempoStack instance.

*Wait for sometime and then delete the instance. Check that the alert TempoStackUnhealthy will be firing in the OCP web console > Observe > Alerting