Set up release pipeline with GitHub Releases and versioning

There is no automated release process. No GitHub Releases are created, no versioning automation, no changelog generation.

**Required:**
- Tag-triggered release workflow
- Automated GitHub Release creation with attached artifacts
- Changelog generation (e.g., release-please or similar)
- Version synchronization across Cargo.toml, tauri.conf.json, and package.json

Start by inspecting Cargo.toml, tauri.conf.json, and package.json to understand their current version fields and how artifacts are built. Then review the repository's GitHub Actions configuration, if present, and define the tag-triggered release flow. Done means releases include generated changelogs and artifacts, with synchronized versions across all three files.

Written by the indexing model from the issue text.