Add health checks to Rabbit and Postgres to prevent race conditions

[MoralCode]

This avoids some race conditions with the startup process that could create issues, especially on first initialization as noted in #3548 but also observed by me (rabbit had some

Description

• Please include a summary of the change.

This PR fixes #3548
This pr also fixes #3612 (i think)

Thanks to @Sukuna0007Abhi and @guptapratykshh for submitting PRs on this that each addressed different parts of the issue. This PR is the combination of both works and you have both been credited in the commit message

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

[MoralCode]

this is now part of our prod config.

[MoralCode]

Copilot analysis of failed job:

The job failed because RabbitMQ could not read its ".erlang.cookie" file due to a permission error:
Code

Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces

theory: Seems to be due to the container not running as root

[sgoggins]

LGTM

[sgoggins]

@MoralCode : DO we think we should solve for this cookie error? It seems like it needs to be fix for the docker deployments to remain stable.

[sgoggins]

@MoralCode : I can see running as root would likely fix the podman issue, but since we don't care about rabbitmq persisting its queues across startups for Augur, I think we could configure it to use the /tmp directory instead.

[MoralCode]

If we want to just merge the postgres health check and gitconfig error fix, we should reopen #3559 since thats what that PR does.

I have not looked into this CI rabbit issue, so maybe the rabbit health check should be a separate PR.