Fixes the tests/examples of this repo. A UNC path as working directory doesn't work because the build commands of our examples invoke `cargo` on the dora repo. The dora repo uses wildcards in the member list in the top-level Cargo.toml, which are ignored in UNC-paths. Thus, `failed to load manifest for workspace member` errors occur.
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```
The previous machine ID is still used, but optional. Users don't need to ensure that the chosen machine IDs are unique anymore because they are augmented with a UUID.