[BUG] Starting version 2.20.3 using --wait does not update "waiting" progress

[talf]

Description

Running docker compose > v2.20.2 while using --wait for healthchecks, results in the "started" message but does not switch to "waiting". It actually waits and exists if all checks were successful, but the display is frozen.

Steps To Reproduce

1. Define docker-compose.yaml with healthcheck
2. run docker-compose up -d --wait

expected results:
after the container starts, it should switch to "waiting" and continue with counting seconds

actual result:
display stuck on "started"

Compose Version

Docker Compose version v2.23.0-desktop.1

Docker Environment

Client:
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     /Users/talf/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.23.0-desktop.1
    Path:     /Users/talf/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/talf/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/talf/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.9
    Path:     /Users/talf/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/talf/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/talf/.docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.9
    Path:     /Users/talf/.docker/cli-plugins/docker-scout

Server:
 Containers: 30
  Running: 20
  Paused: 0
  Stopped: 10
 Images: 144
 Server Version: master
 Storage Driver: stargz
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.4.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 9
 Total Memory: 27.37GiB
 Name: linuxkit-16754f6243a9
 ID: 45976db3-fb9b-42eb-8daf-9b3987414e37
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 292
  Goroutines: 361
  System Time: 2023-12-25T10:05:21.861581333Z
  EventsListeners: 15
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Registry: https://index.docker.io/v1/
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

Anything else?

versions <=2.20.2 work as expected.
This is true for both the osx compose version and the versions downloaded directly from linux repos such as apk or apt.

[ndeloof]

this was fixed by #11357