fix: debounce now playing toast to show correct track metadata

[endafk]

Problem

When pressing next/previous, the now playing toast shows the previous track instead of the new one.

Root cause

Some MPRIS players (notably Spotify and Google Chrome) emit postTrackChanged in two D-Bus phases:

1. First signal: mpris:trackid updates to the new track, but xesam:title/xesam:artist still carry the old track's values
2. Second signal: the actual title and artist arrive

onPostTrackChanged was firing immediately on phase 1, reading stale metadata and displaying the wrong song in the notification.

Fix

Defer the toast via a Timer { interval: 300 }. The handler now calls nowPlayingTimer.restart() instead of showing the toast directly. If postTrackChanged fires again within 300ms (the second metadata update), the timer resets — so only one notification fires, after the metadata has settled.

[Copilot]

Pull request overview

This PR fixes incorrect “Now Playing” toast metadata by debouncing MPRIS postTrackChanged handling so notifications fire after player metadata settles (notably for Spotify’s two-phase D-Bus updates).

Changes:

• Route postTrackChanged handling through a 300ms Timer to debounce the toast.
• Add QtQuick import to use Timer.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[soramanew]

Hmm, I use spotify and the media toasts work fine. There is only one on song change and it displays the track correctly.

[endafk]

Hmm, I use spotify and the media toasts work fine. There is only one on song change and it displays the track correctly.

I pretty use Gapless(g4music) and chrome(Youtube and Youtube Music) and I get a toast of the previous song whenever I use next. Whenever music stops. I also receive a toast of the music that was playing before I stoppped. Everytime there is an update, I have to redo the 300ms delay manually on the qml file