So, As mentioned
[here](https://github.com/dora-rs/dora/pull/913#issuecomment-2747339237).
I did these changes and tried it with "Hennzau" fork and it seems to be
working fine.
```Checking for updates...
Checking target-arch... x86_64-unknown-linux-gnu
Checking current version... v0.3.10
Checking latest released version... v0.3.11
New release found! v0.3.10 --> v0.3.11
New release is compatible

dora release status:
  * Current exe: "/home/arlott/gsoc/dora/dora/target/debug/dora"
  * New exe release: "dora-cli-x86_64-unknown-linux-gnu.tar.gz"
  * New exe download url: "https://api.github.com/repos/Hennzau/dora/releases/assets/240150528"

The new release will be downloaded/extracted and the existing binary will be replaced.
Do you want to continue? [Y/n] Y
Downloading...
[00:00:03] [========================================] 15.41MB/15.41MB (0s) Done
Extracting archive... Done
Replacing binary file... Done
Successfully updated Dora CLI to version: 0.3.11```

First step towards versioning the message definitions indepedently.

Allows to override the log level through the `RUST_LOG` env variable.

Forwarded by coordinator

There is a current vulnerability (low severity) and the crate appears to be unmaintained. Since Rust 1.70, we should be able to use the new `IsTerminal` trait of the standard library instead.

test new crates version release

test rc 2 version

fix version typo

Test crates.io new dora tag release

Remove unused dependencies

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

Bumps [webbrowser](https://github.com/amodm/webbrowser-rs) from 0.8.0 to 0.8.3.
- [Release notes](https://github.com/amodm/webbrowser-rs/releases)
- [Changelog](https://github.com/amodm/webbrowser-rs/blob/main/CHANGELOG.md)
- [Commits](https://github.com/amodm/webbrowser-rs/compare/v0.8.0...v0.8.3)

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

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

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

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.

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

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

To avoid name collision with Python package.

The executable is renamed back to `dora` in the release archive for easier usage.