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 .

This fix the CI that I unfortunately broke at #667

By versioning the `dora-message` crate individually, we can use the
semver rules to encode which versions are compatible. This way, we can
allow different versions of dora to work together (e.g. CLI version can
be different than node API version), as long as the message formats are
compatible. Breaking message format changes are signaled by a
semver-incompatible release of `dora-message`. For example, 0.4.0 is not
compatible with 0.3.5.

One alternative approach could be to use the main version to signal
compatibility, i.e. the common version that we use for all dora crates.
This has the disadvantage that we might need to bump the minor version
of the main dora crate every time we want to change the message format
in a breaking way. As we still expect semi-regular breaking changes to
the message format in the near future, we want to avoid this churn. Once
we consider the message format more stable, we plan to revisit this
approach.

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

TODO

- [x] Update release script: We should not try to publish the
`dora-message` crate if there is no new version.
- [x] Relax version checks to only compare major/minor version
(according to semver compatibility rules).

First step towards versioning the message definitions indepedently.

Decouples the `dora-message` version from the version of the other `dora-*` crates. This allows us to use semver-versioning for the `dora-message` crate to encode message compatibility across dora versions.

First step towards versioning the message definitions indepedently.

Ros2-bridge action attempt

Add basic log forwarding from daemon to CLI