fix(service): wait for rabbitmq amqp listener in healthchecks

rabbitmq-diagnostics ping succeeds before the AMQP listener on 5672
is open, so dependent services started too early and failed with
connection refused. Use check_port_connectivity with a start period
in the hatchet, plane, rabbitmq and mautic5 templates.

Closes #12105

templates/compose/hatchet.yaml

@@ -70,10 +70,11 @@ services:
       - RABBITMQ_DEFAULT_PASS=$SERVICE_PASSWORD_RABBITMQ
       - PORT=${RABBITMQ_PORT:-5672}
     healthcheck:
-      test: rabbitmq-diagnostics -q ping
+      test: rabbitmq-diagnostics -q check_port_connectivity
       interval: 5s
       timeout: 30s
-      retries: 10
+      retries: 20
+      start_period: 60s
     volumes:
       - rabbitmq-data:/var/lib/rabbitmq/
 

templates/compose/mautic5.yaml

@@ -27,10 +27,11 @@ services:
     environment:
       - 'RABBITMQ_DEFAULT_VHOST=${RABBITMQ_DEFAULT_VHOST:-mautic}'
     healthcheck:
-      test: rabbitmq-diagnostics -q ping
+      test: rabbitmq-diagnostics -q check_port_connectivity
       interval: 5s
       timeout: 30s
-      retries: 10
+      retries: 20
+      start_period: 60s
     volumes:
       - 'rabbitmq-data:/var/lib/rabbitmq'
   mautic_web:

templates/compose/plane.yaml

@@ -229,10 +229,11 @@ services:
     volumes:
       - rabbitmq_data:/var/lib/rabbitmq
     healthcheck:
-      test: rabbitmq-diagnostics -q ping
+      test: rabbitmq-diagnostics -q check_port_connectivity
       interval: 30s
       timeout: 30s
       retries: 3
+      start_period: 60s
 
   # Comment this if you using any external s3 compatible storage
   plane-minio:

templates/compose/rabbitmq.yaml

@@ -17,9 +17,10 @@ services:
     ports:
       - ${PORT}:5672
     healthcheck:
-      test: rabbitmq-diagnostics -q ping
+      test: rabbitmq-diagnostics -q check_port_connectivity
       interval: 5s
       timeout: 30s
-      retries: 10
+      retries: 20
+      start_period: 60s
     volumes:
       - rabbitmq-data:/var/lib/rabbitmq/