Bumps [capnp](https://github.com/capnproto/capnproto-rust) from 0.14.9 to 0.14.11.
- [Release notes](https://github.com/capnproto/capnproto-rust/releases)
- [Commits](https://github.com/capnproto/capnproto-rust/compare/capnp-v0.14.9...capnp-v0.14.11)

---
updated-dependencies:
- dependency-name: capnp
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

This commit is an initial draft at fixing #147. The error is due to the
fact that pyo3 has linked the libpython from the compilation and not
trying to use libpython that is available in `LD_LIBRARY_PATH`.

The current only solution to disable the linking is to use the `extension-module` flag.
This requires to make the python `runtime-node` packaged in a python library.
The python `runtime-node` should also be fully compatible with the other operators in case we want hybrid runtime.

The issue that i'm facing is that. Due to the packaging, I have to deal with the `GIL` that is present from the start of
`dora-runtime` node. This however makes the process single threaded wich is impossible.

So, I have to disable it, but when I do, I have a race condition:
```bash
Exception ignored in: <module 'threading' from '/usr/lib/python3.8/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 1373, in _shutdown
    assert tlock.locked()
AssertionError:
```
The issue is the same as https://github.com/PyO3/pyo3/issues/1274

To fix this issue, I'm going to look again at the different step to make this work.

But this is my current investigation.

Use cache instead of downloading file each time

Use the new request/reply communcation layer and its TCP-based implementation for sending control messages from the CLI to the dora coordinator.

Queries the list of running dataflows from the coordinator and prompts the user to choose one.

Implement a C++ operator API

This is particularly useful if internet is down.

Allow configuring the `dora up` behavior through a `dora-config.yml` file

This PR makes it possible to use command line argument as custom node source.
This is very useful when the program is dependant on some environment variable
to be run. Exemples are: ROS/setup.bash and Python/Conda activate.

Custom node source can now be:
- a path: `./target/debut/abcd`
- a program in path: `rosrun`
- a url: `https://github.com/dora-rs/dora/releases/download/v0.0.0-test.4/rust-dataflow-example-node`
- or at the last resort a command line program: `source setup.bash && roslaunch velodyne_pointcloud VLP16_points.launch`

All those sources can have arguments `args` passed through the `args` field of the node. This args field
is recommanded when using a path as it will better manage the different OS.

Pinning zenoh git version to fix recompilation of the `dora-api-operator` when it
is a user dependency.

Based on Rust API using `cxx` for bridging.

Parsing as URI does not work for relative paths, e.g. `../../foo`.

Makes it possible to set an URL as operator source. The `dora-runtime` will then try to download the operator from the given URL when the dataflow is started.

Allows replying to requests. We use this to send the dataflow UUID back to the CLI after starting it.

* Add a `dora-python-operator` crate to hold utils functions for dora python

* Remove python serialisation and deserialisation from `dora-runtime`

* Update `python` documentation

Implement CLI `start` and `destroy` and make coordinator a daemon

* add opentelemetry feature to python op

* modify `python-dataflow` to test opentelemetry

* change `timer` topic to `tick`

* adding tracing to `shared_libraries`

* example install refactoring

* Rename `input` to `dora_input` for python ex

Start creating command line interface with `check`, `build`, `graph` and `templates` commands