openlogi-device: replace tokio::time with a wasm-portable timer

`openlogi-device` uses `tokio::time` for inventory/write timeouts (~10 sites). On `wasm32-unknown-unknown` these panic at runtime — the wasm CI job is a `cargo check` and cannot see it.

Candidate: `futures-timer`, which costs a global timer thread on native — weigh that against a cfg-split timer shim. Whatever the pick, the constraint is one timer story for native and wasm, not per-call-site cfg.

Start in the openlogi-device crate by locating its roughly 10 tokio::time timeout sites and checking how the wasm32-unknown-unknown target currently handles them. Compare futures-timer with a cfg-split timer shim, then verify that all sites use one timer story and that wasm no longer panics while native behavior is preserved.

Written by the indexing model from the issue text.