Healthchecks for sidekiq + misc fixes

[fbacall]

Summary of changes

• Add healthcheck to sidekiq docker container
• Ensure db healthcheck uses correct database user
• Ensure dev containers are restarted
• Bump vulnerable gem versions
• Move gem auditing after tests (so they run regardless)

Checklist

• I have read and followed the CONTRIBUTING guide.
• I confirm that I have the authority necessary to make this contribution on behalf of its copyright owner and agree to license it to the TeSS codebase under the BSD license.

[Copilot]

Pull request overview

This PR improves container/runtime robustness by adding healthchecks and restart policies to the Docker Compose setup, while also updating dependencies and adjusting CI ordering to ensure tests aren’t blocked by gem auditing.

Changes:

• Add/revise Docker Compose healthchecks (DB user fix; Sidekiq healthcheck added) and add restart: unless-stopped to dev services.
• Bump vulnerable gem versions in Gemfile.lock.
• Move bundle-audit step to the end of the GitHub Actions test workflow so tests run even if auditing fails.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
Gemfile.lock	Bumps gem versions (e.g., concurrent-ruby, faraday) to address vulnerability/patch updates.
docker-compose.yml	Adds dev container restart policies; updates Postgres healthcheck user; adds Sidekiq healthcheck.
docker-compose-prod.yml	Updates Postgres healthcheck user; adds Sidekiq healthcheck in prod compose.
.github/workflows/test.yml	Moves gem audit step after unit/system tests so auditing doesn’t prevent tests from running.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.