Allow timedb container to wait and recover from rabbitmq issues
Sometimes rabbitmq is not available (uninstalled) or hasn't fully started yet. This currently causes the mapcache timedb container to crash because it can't listen for messages. There should be a while or for loop that counts how many times this failure is allowed before giving up. This should give kubernetes time to restart the pod a couple times before completely giving up on it (CrashLoopBackoff).