Missed in the earlier bump pass. Confirmed every other version pin
reads 1.2.5: src-tauri/Cargo.toml, src-tauri/Cargo.lock,
src-tauri/tauri.conf.json, package.json, package-lock.json,
snapcraft.yaml, packaging/flatpak/com.blitzfc.qbz.metainfo.xml
(top <release> entry); the only remaining "1.2.4" string in the tree
is the historic release entry in metainfo.xml, which is correct.
cc
The package's `postInstall` wraps the installed `qbz` binary with
`LD_LIBRARY_PATH` so it can `dlopen(libayatana-appindicator3.so.1)` at
runtime. Inside `nix develop`, users run `target/debug/qbz` directly
without that wrapper, so the tray init panics at startup.
Add a `shellHook` that mirrors `postInstall`'s library path.
Same root cause as the previous LIBCLANG_PATH fix: `inputsFrom` makes
dependencies available at build time but does not set runtime/env vars
the way the installed wrapper does.
Refs #312.
cc
`inputsFrom` does not propagate the package's `env.*` attributes into
the dev shell, so running `npm run tauri dev` inside `nix develop`
failed at `mupdf-sys(build)` with "Unable to find libclang".
Re-export LIBCLANG_PATH on the shell itself.
Closes#312.
cc