Improve ddev failure time when start isn't working out

[rfay]

Describe the bug

If ddev is broken, in many cases the container will immediately exit.

But ddev sits there waiting for all containers to be ready for really quite a long time.

To Reproduce

Break a ddev database.

• ddev ssh -s db
• rm /var/lib/mysql/mysql/*.MYD
• ddev rm
• time ddev start

The ddev-dbserver container will exit immediately, meaning we failed to start. But the ddev start times out only after 72 seconds.

Expected behavior

A broken container is enough to know that the ddev start didn't work out, and will simplify the debugging process. It could even provide the ddev logs from the broken container. In this case:

Screenshots
If applicable, add screenshots to help explain your problem.

Version and configuration information (please complete the following information):

• Host computer OS and Version: [e.g. Windows 10, macOS High Sierra]
• Docker version information (use docker version) and insert it here.
• ddev version information (use ddev version)
• config.yaml contents for the misbehaving project
• Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? If so, have you tried without them?

Additional context
Add any other context about the problem here. Thanks!