Improve debugging of the local dev environment to detect errors in containers startup and ensure proper bootstrapping

Overview of the Feature Request

We have recently encountered issues in the execution of the development environment. Specifically regarding Solr, since it did not seem to have been configured correctly even though the Dataverse application was accessible.

When creating a dataset, we encountered the following error:

Debugging the environment and its dependencies is currently not very accessible, since the run-env script executes the containers in detached mode and the container logs do not appear in the console.

It would also be good to improve in some way (This can potentially affect images and go out of frontend scope) the Dataverse health check to make sure that not only the application is healthy, but also its dependencies (Solr, Postgres, etc.). This way configbaker would finish when all containers are properly initialized (application + dependencies).

What inspired the request?

• Recent issues reported about the dev-env environment

What existing behavior do you want changed?

• Development environment

Any brand new behavior do you want to add to Dataverse?

N/A

Any open or closed issues related to this feature request?

Start by reading and running the run-env script to understand how containers are launched and why their logs are hidden. Trace how configbaker determines readiness, including the Dataverse application and dependencies such as Solr and Postgres. Done means startup failures are visible and bootstrapping waits until the required services are healthy.