[bug]: Replay starts test-set execution before the containers are started

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behavior

In replay mode the execution of test starts before the docker application is started.
Expected behavior for keplay is to wait for docker application to start and then execute the test-set.

### Steps to reproduce

1. Go the gin-mongo sample app
2. Make sure you require some time to start the container while running keploy
3. Run the command ```keployV2 test -c "docker compose up" --containerName "ginMongoApp" --buildDelay 100s```

### Environment

None

### Version

Cloud

### Repository

keploy

Reproduce this with the gin-mongo sample app using `keployV2 test -c "docker compose up" --containerName "ginMongoApp" --buildDelay 100s`. Trace the replay startup and test-set execution flow to identify why execution does not wait for the Docker application. Done means the test-set starts only after the application containers are ready, with coverage for the delayed-start case.

Written by the indexing model from the issue text.