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

First step towards versioning the message definitions indepedently.

When dropping the `DoraNode`, it waits for the remaining drop tokens. This only works if all the dora events were already dropped before. With the Python GC, this is not guaranteed as some events might still be live on the heap (the user might even use them later). In such cases, we waited until we ran into a timeout, which resulted in very long exit times (see https://github.com/dora-rs/dora/issues/598).

This commit fixes this issue by adding a reference-counted copy of the `DoraNode` and `EventStream` to every event given to Python. This way, we can ensure that the underlying `DoraNode` is only dropped after the last event reference has been freed.

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.

Update Pyo3 bounds

The deprecation warning states:

> code not using the `GIL Refs` API can safely remove the use of `Py::new_pool`

All GIL Refs usage have been removed, so this should be fine.

Arrow needs to be upgraded alongside pyo3 because they both link to python.

NOTE: Arrow marked `ffi::from_ffi` unsafe.
https://github.com/apache/arrow-rs/pull/5080

the global meter.

features

Ensures that all raw data has at least an alignment of 128.

Buffer capacity is always 0 if the buffer is allocated externally. Also, we don't want to allocate unneccessary extra space if only parts of a buffer a used (e.g. when slicing).

This PR/commit adds documentation for the send_output method.

Follow up discussion: https://github.com/orgs/dora-rs/discussions/317#discussioncomment-6475816

add an attribute that disables the dead_code lint

Previous implementation of the runtime would link `libpython` even though it
might not be required.

This commit put pyo3 dependency under a feature flag that is only active if
the runtime is called from python for a python operator.

This fix:
- https://github.com/dora-rs/dora/actions/runs/4879188973/jobs/8705515472
- https://github.com/dora-rs/dora/issues/280#issuecomment-1534058207
- and https://github.com/dora-rs/dora-drives/issues/58#event-9162532660

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.