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.

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.

Instead of doing an additional copy to send them from the operator thread to the runtime thread.

This commit uses the new `allocate_data_sample` and `send_output_sample` methods introduced in d7cd370.

This is mostly about convenience when working with arrow data types, as the data is still being copied once.

Reuse same event type as for Python node API.

The previous approach no longer works on `pyo3` v0.18 because `setattr` now requires a `IntoPy<Py<PyString>>` as key.

This commit adds the ability to use the `opentelemetry` feature flag at
runtime by using the env variable `DORA_TELEMETRY`. Using environment
variable reduce the need to do some argument drilling between our
different process as well as making configurable in the YAML at no cost.

Usage:

```bash
docker run -d -p6831:6831/udp -p6832:6832/udp -p16686:16686 jaegertracing/all-in-one:latest
DORA_TELEMETRY=true dora-daemon --run-dataflow dataflow.yml
```

Current limitation:

- The telemetry currently only work with Jaeger on the local network with
default port: 6831 and 6832.

Validate yaml when reading

After adding #236 , error of initialization is shadowed by bailing on
the sender channel.

Bailing used to happen here: ccec196234/binaries/runtime/src/lib.rs (L136)

This makes it hard to debug.

This PR will push the error into the sender channel, and report any error
of initialization making it easier to debug.

Now the channel is used without error, but any error of initialization
will bail the runtime here: ccec196234/binaries/runtime/src/lib.rs (L137)

Make queue length configurable through the dataflow file

The `tracing` feature just enables the tracing subscriber, the `telemetry` feature the `opentelemetry` integration.

The intent of this commit is to remove the quantity of log that is being pushed to user.

This commit removes the redeclaration of a set up tracing methods to centralise
the tokio-tracing subscriber within the extension crate. It also add the
feature to filter information based on Environment variable.
This makes it possible to define the log level for tokio tracing like
this:
```
RUST_LOG=debug dora-daemon --run-dataflow dataflow.yml
```

I have also unified the feature flag to make it easier to manage tracing features among the workspace.

I did not change the default behaviour of tracing in our crates and therefore by
using the command above you should get the same tracing log as before.

fix merge conflict generated

Fixes a deadlock issue when the `incoming` channel is closed first. The problem was that the `send_out_buf` was set to `Fuse::terminated` without breaking the loop, so on the next loop iteration both futures were already terminated.

This causes the `send_out_buf` future to completely starve.

We now report other event types as well. Right now, the only other event type is `Stop`, but we can extend this in the future.