Adjust rabbitmq probes to better reflect its actual state

This PS looks to make a few small tweaks to the rabbitmq probes so
that its health and readiness is more reflective of what is actually
happening inside the container. We were previously seeing instances
of the pod marked as ready before it actually was.

Change-Id: If48ec02d4050f7385e71c2e6fe0fff8f59667af4

rabbitmq/templates/bin/_rabbitmq-liveness.sh.tpl

@@ -20,5 +20,5 @@ if [ -f /tmp/rabbit-disable-liveness-probe ]; then
    exit 0
 else
    timeout 5 bash -c "true &>/dev/null </dev/tcp/${MY_POD_IP}/${PORT_AMPQ}"
-   exec rabbitmqctl status
+   exec rabbitmqctl node_health_check
 fi

rabbitmq/templates/bin/_rabbitmq-readiness.sh.tpl

@@ -19,5 +19,5 @@ set -e
 if [ -f /tmp/rabbit-disable-readiness ]; then
    exit 1
 else
-   exec rabbitmqctl status
+   exec rabbitmqctl node_health_check
 fi

rabbitmq/templates/statefulset.yaml

@@ -217,7 +217,7 @@ spec:
               command:
               - /tmp/rabbitmq-readiness.sh
           livenessProbe:
-            initialDelaySeconds: 30
+            initialDelaySeconds: 60
             timeoutSeconds: 10
             exec:
               command: