v1.1.6 — Bitwarden CLI detection fix for Tauri-launched apps

Fix

When CodeTerm was launched via Tauri (or any other minimal-PATH desktop launcher), the Bitwarden integration could not locate the `bw` CLI. macOS app launchers strip `PATH` down to `/usr/bin:/bin:/usr/sbin:/sbin`, which excludes Homebrew, npm-global, and other common install locations.

What changed

`secrets::bitwarden` now augments `which`-based lookup with a curated list of known install paths per platform:

• macOS: `/opt/homebrew/bin`, `/usr/local/bin`, `/.npm-global/bin`, `/.bun/bin`, …
• Linux: `/usr/local/bin`, `~/.npm-global/bin`, …
• Windows: `%LOCALAPPDATA%\npm`, `%APPDATA%\npm`, …

If `bw` exists at any of those paths, the integration uses it directly even when `PATH` does not include the directory.

Verification

• 32 `secrets::bitwarden` unit tests pass.
• Live verified by launching the debug binary with `PATH=/usr/bin:/bin:/usr/sbin:/sbin` and confirming Bitwarden detection via `/opt/homebrew/bin/bw`.