This command is useful for testing examples with multiple daemons.

It might take a short time until the daemon is connected to the coordinator after start-up. This could lead to issues when using `dora up` in a script because a subsequent `dora start` command might fail when the daemon is not connected at that point.

This commit fixes this issue by waiting until the coordinator confirms that a daemon is connected before returning from `dora up`.

Avoids a cargo warning.

I added a test to confirm the output matches the old.

Fixes clippy warning clippy::format_collect
https://rust-lang.github.io/rust-clippy/master/index.html#/format_collect

We are not interested in the local bind address of the daemon. Instead, we want to use the IP address under which the daemon is available from other machines.

This should also avoids the issue that connecting to 0.0.0.0 is not possible on Windows (we want to use 0.0.0.0 as default bind address).

This reverts commit 1ba763cd67.

This reverts commit 4af82a4833.

clients can not connect to `0.0.0.0` on windows.

Ref: #459

Ref: #459

This commit makes it possible to specify the conda env that we want to use in
a specific operator.

```yaml
  - id: robot
    operator:
      python:
        source: ../operators/robot.py
        conda_env: robomaster
```

This will call:
```bash
conda run -n robomaster python -c "import dora; dora.start_runtime()"
```

Send runs artefacts into a dedicated `out` folder

the global meter.

Bump 0.3.2-rc2

This commit make it possible to check the logs as follows:

```bash
dora logs object_detection
```

If more than one dataflow is running, we will inquire for which dataflow to use.

Tokio background tasks are canceled when the program exits, so we need some additional synchronization to ensure that the `DestroyResult` is actually sent out.

This reverts commit 5c16c59b6f.