start-blueos-core: machineid-cli fails on orange pi 5 plus

```
root@orangepi5plus:~# RUST_BACKTRACE=1 machineid-cli --key blueos --parts cpu-cores cpuid mac-address > /etc/blueos/hardware-uuid thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: HWIDError { message: "No such file or directory (os error 2)", kind: "NotFound" }', src/main.rs:137:43
stack backtrace:
0: rust_begin_unwind
at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/panicking.rs:67:14
2: core::result::unwrap_failed
at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/result.rs:1651:5
3: machineid_cli::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```

Reproduce the shown machineid-cli command on an Orange Pi 5 Plus, then inspect src/main.rs at line 137 and the full backtrace to locate the missing path failure. Done means the command completes without panicking and produces the expected hardware UUID output in /etc/blueos/hardware-uuid.

Written by the indexing model from the issue text.