Dapr in Testcontainers should use a wait strategy based on healthz/outbound #1104
Description
Expected Behavior
Currently we could run into race conditions when using Dapr Testcontainer implementation when it is used across multiple integration tests. We should use Testcontainers Wait Strategy to make sure that container is marked as ready ONLY when all the components are properly initialized.
Actual Behavior
There tests based on current Dapr Testcontainer could run into random failures because of race conditions when running the containers, since there is no explicit waiting to make sure container is properly initialized.
Steps to Reproduce the Problem
Create a few tests using Dapr Testcontainers and see how tests fail randomly.
Release Note
RELEASE NOTE: