v3.2.5 issue with the `--wait` in the default setup command

Version 2.3.5 changes the behavior by using `--wait` in the default setup command (see: https://github.com/avast/pytest-docker/pull/129).

Currently, I don't have any details, but this change breaks most likely my automated tests in https://github.com/AlbrechtL/openwrt-docker/blob/master/test/tests/openwrt_docker_test.py. I always receive `container openwrt is unhealthy`. See for example here: https://github.com/AlbrechtL/openwrt-docker/actions/runs/19550202099/job/55986920058.

Before version 2.3.5 it was working fine.

Start with the default setup command and the v2.3.5 change described in PR 129, then reproduce the failure using openwrt_docker_test.py and the linked GitHub Actions run. Compare behavior before and after the change, focusing on the `--wait` option and the `container openwrt is unhealthy` result. Done means the regression is reproduced and its cause is identified with a targeted test or clear evidence.

Written by the indexing model from the issue text.