Add support for distributed deployments with multiple daemons

The coordinator is our control plane and should not be involved in data plane operations. This way, the dataflow can continue even if the coordinator fails.

Make log level filtering be `WARN` or below

Allow the issue labeler to write issues

The path should also be valid on the receiving node, which might run in a different directory.

We still need to pass the path through a new `working_dir` field as we haven't figured out deployment of compiled nodes/operators yet.

Fix typo

Add automatic issue labeler to organize opened issues

Filter default log level at `warn` for `tokio::tracing`

Add a support matrix with planned feature to clarify dora status

This PR is based on Github Regex labeler https://github.com/marketplace/actions/regex-issue-labeler?version=v3.1 and use a configuration file to set label to issues.

I want to organize issues based on which part of dora they affect.

Integrate `dora-runtime` into `dora-daemon`

Removes the separate `dora-runtime` binary. The runtime can now be started by passing `--run-dora-runtime` to `dora-daemon`. This change makes setup and deployment easier since it removes one executable that needs to be copied across machines.

CLI: Improve error messages when coordinator is not running

This information is not relevant to users and might confuse them.

We now exit with an error exit code again when no coordinator is running.

[Python] Show node name in process and put Traceback before the actual Error for more natural error

Allow passing runtime path via coordinator

In #229, I renamed `eyre::eyre!("{err}{traceback}")`  where it should have `eyre::eyre!("{traceback}\n{err}")` . This PR fix this issue.

This Pull Request also add the name of the node process at the end of the process call to help with debugging.