DSH Desktop v0.1.1

Bump the version to 0.1.1

Four places have to agree, and only one of them is enforced anywhere: the tag has
to match `version` in tauri.conf.json or the updater treats the release as not
newer and existing installs ignore it. Nothing in the workflow checks this, so it
fails silently — the release builds, publishes, and simply never reaches anyone.

Cargo.toml and package.json are kept in step so the binary metadata and the npm
manifest do not disagree with the bundle, and both lockfiles record their own
package's version so they move too. `npm install --package-lock-only` also filled
in `license` and `engines`, which package.json gained after the lockfile was last
written; no dependency versions changed.

Verified: cargo check builds at 0.1.1, 29 tests pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>