[tempo-distributed] Container has the same readiness and liveness probe

[drisbee]

The Loki service is currently lacking proper probes, leading to potential issues with monitoring, health checks, and graceful handling of service disruptions. Probes play a critical role in ensuring the stability and reliability of services within our Kubernetes cluster.

This issue was discovered while scanning the helm chart via kube-score:
https://github.com/zegl/kube-score/blob/master/README_PROBES.md

The components with equal probes are:

apps/v1/Deployment grafana-tempo-compactor
apps/v1/Deployment grafana-tempo-distributor
apps/v1/Deployment grafana-tempo-metrics-generator
apps/v1/Deployment grafana-tempo-querier
apps/v1/Deployment grafana-tempo-query-frontend
apps/v1/StatefulSet grafana-tempo-ingester
apps/v1/StatefulSet grafana-tempo-memcached
Is there any reason for not having proper probes for the given components? If not, what would be the recommendation?