Develop docker healthchecks

[ninjamonkey198206]

Added healthchecks to the docker-compose file for nginx, redis, postgres, and mongodb

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.43%. Comparing base (9f2f23f) to head (bf68d12).
⚠️ Report is 838 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1211   +/-   ##
========================================
  Coverage    81.43%   81.43%           
========================================
  Files          116      116           
  Lines         7747     7747           
========================================
  Hits          6309     6309           
  Misses        1438     1438           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ninjamonkey198206]

Unfortunately I think this will have to be done in stages, as I'm having trouble getting nats and mesh to play nice for testing.

[ninjamonkey198206]

@sadnub the nginx one clued me into the issue with the duplicate nginx.conf entry that was going around, and gives a heads-up if the containers go funky, which I've noticed happens sometimes after a host system reboot.

The nginx container would be running, and everything else would show as up and running, but nothing would work. The simple health check here would then show the nginx container as running, but not healthy.

I'm sure there are more in-depth methods, but I think this would be a good start.

I think I saw a monitoring URL somewhere, in fact...

[CLAassistant]

All committers have signed the CLA.

[stavros-k]

Suggested change

	test: [ "CMD", "pg_isready", "-U", "tactical", "-d", "tacticalrmm" ]
	test: [ "CMD", "pg_isready", "-U", "$$POSTGRES_USER", "-d", "$$POSTGRES_DB" ]

Maybe use env's here?