Thwy were an error of typecasting within the C++ node input.

This fixes #403

I have not adressed all input type as I think a solution based on arrow FFI would be better.

By default, cargo reruns build scripts whenever any file of the package changes. This led to lots of unnecessary rebuilds of the `dora-operator-api-c` crate. The reason is that crate has a build script that updates the `operator_types.h` file, which is considered as a modification by cargo. So it reruns the build script on the next `cargo build` or `cargo run` command, which leads to subsequent rebuilds of all crates that depend on `dora-operator-api-c`.

This commit fixes this issue by instructing cargo to never rerun the build script (through a special `println`). This way the package is considered 'fresh' on rebuilds. Cargo will still rerun the build script when the `dora_operator_api_types` crate changes, so the `operator_types.h` file still stays up-to-date.

Reuse same event type as for Python node API.

test new crates version release

test rc 2 version

fix version typo

Test crates.io new dora tag release

Removing those path make it easier to move package, reduce path management
reduce complexity and make it easier to export crates to `crates.io`

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

This way, we don't need to update the version manually in all sub-crates on every release.

Implement a C++ operator API

Useful in case of emergencies.

Based on Rust API using `cxx` for bridging.