Json schemas for VSCode YAML Support

Adding python IDE typing

We are not interested in the local bind address of the daemon. Instead, we want to use the IP address under which the daemon is available from other machines.

This should also avoids the issue that connecting to 0.0.0.0 is not possible on Windows (we want to use 0.0.0.0 as default bind address).

This commit makes it possible to specify the conda env that we want to use in
a specific operator.

```yaml
  - id: robot
    operator:
      python:
        source: ../operators/robot.py
        conda_env: robomaster
```

This will call:
```bash
conda run -n robomaster python -c "import dora; dora.start_runtime()"
```

Send runs artefacts into a dedicated `out` folder

Tokio background tasks are canceled when the program exits, so we need some additional synchronization to ensure that the `DestroyResult` is actually sent out.

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

Makes the distinction between raw data and data messages clearer.

Seializing Vec<u8> by default iterate over each element instead of copying
the byte array.

See: https://github.com/rust-lang/rust/issues/31844

Make dataflow descriptor available to Python nodes and operators

The `with_extension` method returns a new path, it does not modify the existing path.

The previous watchdog requests required waiting for a reply, which could slow down the system under load and also lead to false errors on slower systems (e.g. the CI). Because of this, this commit replaces the watchdog requests with asynchronous heartbeat messages, which don't require replies. Instead, we record the last heartbeat timestamp whenever we receive a heartbeat message. We then periodically check the time since the last received heartbeat message and consider the connection closed if too much time has passed.