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

[AlbrechtL]

Version 2.3.5 changes the behavior by using --wait in the default setup command (see: #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.

[eabruzzese]

This also breaks Docker compositions that include run-once-and-exit containers (i.e., initialization containers). For example, I have a rustfs container for object storage, and a rustfs-create-bucket container to create a bucket if it doesn't exist, and then exit 0. This doesn't work with --wait, because it considers all container exits to be failures, regardless of the return code.

For now I think I can just override docker_setup to fix it, though.