In order to simplify testing with a terminal, I have added couple of
simple nodes in the node-hub.

To use:
```bash
cd examples/terminal-dataflow
dora build dataflow.yml
dora start dataflow.yml

# Terminal A
terminal-print

# Terminal B
pyarrow-sender


```

Note that there might be issues with stopping the dataflow and you might
need to use `dora destroy`

# Video example

[Screencast from 2024-08-09
12-41-17.webm](https://github.com/user-attachments/assets/04db8e4f-652e-42a9-a42e-6c49d2ff9fae)

First step towards versioning the message definitions indepedently.

Rewrite README documentation to reflect metadata changes

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

.idea

.idea

README.md and better outputs/inputs

README.md and ultralytics-yolo

fix queue_size and dynamic

README.md

Fix CI

Fix CI

Fix CI

Fix CI

Fix CI

Fix CI

Fix CI

Fix CI

Fix CI

Currently having a custom PyEvent make debugging very hard as fields are hidden within the class PyEvent that is defined within Rust Code.

Python user are getting really confused about this obscure class.

This PR transforms the class into a standard python dictionary.

Run dynamic node

Adding python IDE typing

the Q was answered in review. stopping is unnecessary because the `event_stream` wills top shortly

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

Previously, this dataflow relied on an incorrect shared library.

Minimal conversion from previous operator api to node api.

Ref #474

This commit add an initial dora-rerun extension for visualization of run
using rerun.

This is still experimental and will be improved in the future.

I also added an example that we can try out by:

```bash
cd examples/rerun-viewer
dora start dataflow.yml --attach
```

You might need to install rerun viewer with
```bash
cargo install --force rerun-cli@0.15.1
```

This reverts commit 1ba763cd67.