Run dynamic node

* refuse pass relative path to remote daemon

* add local ip checker in dora start

* delete some additional packages on CI to make enough space available

* add coodinator_is_remote argument

Make dora cli connect to remote coordinator

As discussed in https://github.com/dora-rs/dora/pull/478#discussion_r1610005764

We want to treat the nodes like custom nodes in this case since we plan to deprecate operators.

We plan to (soft-)remove operators and simplify the dataflow YAML file by removing the additional nesting caused by the `custom` field. This commit prepares for that. See #474 for context.

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