Related to #9884

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [napi](https://crates.io/crates/napi) | workspace.dependencies | patch | `3.9.3` → `3.9.4` |
| [napi-derive](https://crates.io/crates/napi-derive) | workspace.dependencies | patch | `3.5.6` → `3.5.7` |

`napi-derive-backend` is bumped transitively in `Cargo.lock` (`5.0.4` → `5.0.5`).

### Note on the `windows-sys` change in `Cargo.lock`

The lockfile also flips a few `cfg(windows)`-only crates (`rustix`, `tempfile`, `errno`, `terminal_size`, `winapi-util`, `nu-ansi-term`) from `windows-sys 0.61.2` to `0.59.0`. This is **not** caused by napi (no napi crate depends on `windows-sys`) and **not** platform-specific — it is reproducible on macOS as well.

It is Cargo lockfile churn: those crates accept a wide `windows-sys` range, so both `0.59.0` (kept alive by `colored`, which requires `<=0.59`) and `0.61.2` (kept alive by `tokio`/`mio`/`console`, which require `^0.61`) are valid. Running `cargo update -p napi` perturbs resolution and re-points those edges onto the already-present `0.59.0` node. Both states are valid and functionally equivalent (these deps are not even compiled on non-Windows targets).

This matches the diff produced by the upstream Renovate PR [#9951](#9951) for the same update.