feat: update version to 1.6.26 and add multilingual window titles

feat: update version to 1.6.25 and add glass opacity and grain settings

- Updated package version in package.json.
- Enhanced Tauri configuration with improved window glass effects.
- Added new fields for glass opacity and grain in settings model.
- Implemented migration for glass opacity and grain settings.
- Updated settings service to handle new glass properties.
- Modified window service to apply glass effects based on new settings.
- Updated app and settings components to include glass opacity slider.
- Added translations for new color options and settings labels.
- Introduced new pink theme with appropriate styles.
- Adjusted CSS for glass effects to utilize new opacity settings.

ci: use winget-releaser@main for release-notes-url support, bump 1.6.24

The @v2 tag predates the release-notes-url input and silently ignored
it, so every manifest was missing ReleaseNotesUrl and winget flagged a
Manifest-Metadata-Consistency notice against published 1.6.12. Pin to
@main, which forwards --release-notes-url to komac.

feat: add theme and glass effect settings

- Introduced a new theme system with multiple color options (amber, blue, emerald, neutral, rose, violet).
- Added glass effect toggle for translucent surfaces.
- Updated localization files for various languages to include new theme and glass effect options.
- Modified settings UI to accommodate new theme and glass effect settings.
- Implemented logic to apply selected theme and glass effect in the application.
- Added database migration to support new theme and glass columns in settings.

feat: update version to 1.6.22 and refactor hotkey migration logic

feat: update version to 1.6.21, enhance database connection handling …

fix: clear default stdout log target, bump 1.6.20

tauri-plugin-log enables a Stdout target by default. The Windows GUI
release (windows_subsystem="windows") has no console, so that target
aborted logger init and the app exited instantly with no output -
1.6.18 and 1.6.19 fail to start on Windows. Call clear_targets() and
keep only the file target (Stdout gated to debug builds).

feat: log panics via custom hook, bump 1.6.19

tauri-plugin-log only captures the log crate facade; Rust panics go
straight to stderr, which the Windows GUI release discards. Install a
panic hook that forwards panic info to log::error! (then chains the
default hook), so the 160-plus expect/unwrap sites leave a trace in the
log file when they fire.

feat: add file logging via tauri-plugin-log, bump 1.6.18

printlog! was just println! with a timestamp, so logs went to stdout
only. The Windows release build sets windows_subsystem="windows",
which detaches the console and discards stdout, so release builds
produced no visible logs and never wrote a file on any OS.

Route printlog! through the log crate and register tauri-plugin-log
with Stdout + LogDir targets, so every existing call site now logs to
both the console (dev) and a rotating file in the app log dir (works in
the Windows release build too). No call sites changed.

fix: sync package-lock with package.json, bump 1.6.17

package.json pinned tailwindcss/@tailwindcss/vite 4.3.1 and prettier 3.8.4
but package-lock.json still resolved 4.3.0/3.8.3. Flathub builds offline
with strict 'npm ci', which rejects the mismatch (ENOTCACHED on
@tailwindcss/vite), failing PRs for 1.6.15 and 1.6.16. Regenerate the
lockfile so npm ci passes, bump to 1.6.17 to trigger a fresh release.