fix(launcher): mute notify file-watcher TRACE flood

[AllDaGearNoIdea]

While debugging the CPU issue, I struggled with asyar.log; 100s of notify::fsevent TRACE lines a second, with nothing helpful saved due to 40kb rotation.

The log plugin doesn't set a global level, so dependencies log at TRACE even in release builds.

This adds notify and notify-debouncer-full to the existing axum/hyper/tungstenite mutes. Warn and above still pass, and fs_watcher/file-index logging is unaffected. Not touching the global level or rotation strategy, just trying to targettedly clean.

Test:

• Run the app, save some files under a watched root, confirm asyar.log no longer fills with notify::fsevent lines
• Confirm asyar's own log lines still appear
• cargo test and the notifications suite green

[gemini-code-assist]

Code Review

This pull request configures the logger in asyar-launcher/src-tauri/src/lib.rs to silence verbose trace logs from the notify and notify_debouncer_full crates to prevent log flooding. The reviewer noted that notify-debouncer-full is not used in the project, making its log-level configuration redundant and potentially misleading, and suggested removing it.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[Xoshbin]

Thanks you 🙏.