Rabbitmq health checks for Bytes integration tests instead of sleep()

[Donnype]

Changes

Attempts to tackle the flaky issues from the Bytes CI. Also see this action for the logs: https://github.com/minvws/nl-kat-coordination/actions/runs/4883917359/jobs/8716061057?pr=761

---

Code Checklist

• All the commits in this PR are properly PGP-signed and verified;
• This PR only contains functionality relevant to the issue; tickets have been created for newly discovered issues.
• I have written unit tests for the changes or fixes I made.
• For any non-trivial functionality, I have added integration and/or end-to-end tests.
• I have performed a self-review of my code and refactored it to the best of my abilities.

Communication

• I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
• I have made corresponding changes to the documentation, if necessary.

---

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.

---

Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.

[ammar92]

Not entirely sure if this is exactly the bottleneck (since we don't have the facts), but it does look very plausible and it's good to have these health checks anyway.

The only thing is we should probably have fewer retries than you suggested since that service shouldn't take that long to load

[Donnype]

@ammar92 check!

[dekkers]

Not entirely sure if this is exactly the bottleneck (since we don't have the facts), but it does look very plausible and it's good to have these health checks anyway.

I remember seeing an amqp error in the tests, so this might be the cause...