[mimir.rules.kubernetes] When mimir is unavailable when the component start, it never tries again

[QuentinBisson]

Request

Component startup should retry when connection to mimir is unavailable during the compoent starts but it does not and we have to manually restart the pod:

ts=2024-06-18T13:27:21.649522346Z level=error msg="failed to list rules from mimir" component=mimir.rules.kubernetes.local err="Get \"http://mimir-ruler.mimir.svc:8080/prometheus/config/v1/rules\": dial tcp 172.31.62.76:8080: connect: connection refused"
ts=2024-06-18T13:27:21.649584571Z level=error msg="starting up component failed" component=mimir.rules.kubernetes.local err="Get \"http://mimir-ruler.mimir.svc:8080/prometheus/config/v1/rules\": dial tcp 172.31.62.76:8080: connect: connection refused"

Use case

We need this because we deploy the agent at the same time as Mimir and we have to manually intervene