This allows using up and start with uv:

## How to use:

```bash
cd examples/python-dataflow
dora up
dora start dataflow.yaml --uv
```

Fixes: https://github.com/dora-rs/dora/issues/780

This would help the CI as well

but keep zenoh log level at WARN level

We use `/` as separator for input mappings in dataflow YAML files (e.g. input: `node/output_id`).

We do support `/` characters in output IDs for runtime nodes. If we allowed `/` characters in node IDs too, splitting a `a/b/c` mapping would no longer be possible (could be node `a` with output `b/c` or node `a/b` with output `c`). Therefore we explicitly error on node IDs containing `/` characters in this commit.

Send an exit message from the daemon to the coordinator on exit. This enables the coordinator to disconnect the daemon properly instead of waiting for a missed heartbeat signal.

This can be useful for debugging

The previous machine ID is still used, but optional. Users don't need to ensure that the chosen machine IDs are unique anymore because they are augmented with a UUID.

Co-authored-by: Philipp Oppermann <dev@phil-opp.com>

bump dora to `0.3.7`

Bump dora to 0.3.7-rc1

Minor dependency fix

Fix typo

Runs a dataflow locally, without requiring any any daemon or coordinator
processes. Multi-machine dataflows are not supported. The default log
level is set to `INFO`, overwriting it is possible by setting the
`RUST_LOG` environment variable.

This exposes the internal `dora daemon --run-dataflow` command that we
use for testing.

This addition was proposed in
https://github.com/orgs/dora-rs/discussions/698#discussioncomment-11125465
.

The second commit adds a ctrl-c handler. On first ctrl-c, we send a stop
command to all nodes. On second ctrl-c, we exit immediately and kill all
spawned nodes. On third ctrl-c, we abort the process directly without
waiting (child processes keep running).

To ensure forward compatiblity

Required when building just the `dora-message` crate

Ensures that we need to update `dora-message` less often.

Make `dora-message` a dependency of `dora-core`, instead of the other way around. This way, we can continue to freely bump the version of `dora-core` with the other workspace crates, without introducing errors such as #708.

Runs a dataflow locally, without requiring any any daemon or coordinator processes.

This exposes the internal `dora daemon --run-dataflow` command that we use for testing.

This addition was proposed in https://github.com/orgs/dora-rs/discussions/698#discussioncomment-11125465 .