[BUG] exo run doesn't make clear that a service has failed to start

[BenElgar]

When an exo run command fails it is unclear that this has happened in the UI.

To Reproduce
Steps to reproduce the behavior:

1. Create a docker-compose file with an error, e.g.

services:
  alpine:
    image: "alpine"
    command: "notacommand"

2. Run exo run docker-compose.yml
   This will output something equivalent to the following and not stop:

❯ dexo run docker-compose.yml
GUI available at: http://localhost:4000/#/workspaces/hah3yrwaa4mz7zp1sj275y5wkm

Expected behavior
Terminate the exo run with a non-zero status code or at least output an error message on stderr.

[brandonbloom]

Related: #21

[BenElgar]

I'll note that docker-compose quits when all containers have terminated and provides an option to quit when any container terminates.