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.

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()"
```

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.

Fix window path error

Simplify operator template and remove type hinting

beautify graph visualisation

Use cargo instead of git in Rust `Cargo.toml` template

By using cargo instead of git, we make compilation not have to git clone
dora project.

This PR/commit adds documentation for the send_output method.

Follow up discussion: https://github.com/orgs/dora-rs/discussions/317#discussioncomment-6475816

Replace unmaintained `atty` crate with `std::io::IsTerminal`

There is a current vulnerability (low severity) and the crate appears to be unmaintained. Since Rust 1.70, we should be able to use the new `IsTerminal` trait of the standard library instead.