[Bug]: Moving a playlist into a folder does nothing — set_playlist_folder is never called

### What happened? I created a folder on the Playlists page, then tried to move an existing playlist into it via the "…" menu → "Move to folder" → clicking the folder in the popup. Nothing happens — the playlist stays outside the folder, even after restarting the app. I tried it twice (moving an existing playlist, and creating a new playlist while a folder was involved) and restarted the app both times; the folder is still empty. I exported the logs right after doing this. `create_folder` shows up fine, but `set_playlist_folder` never appears anywhere in the log. Both functions are wrapped in `#[tracing::instrument]` in `crates/db/src/backend/writes.rs`, so if the call had actually reached the backend it should have logged the same way `create_folder` did. This suggests the click in the "Move to folder" popup isn't actually triggering the backend call — possibly in `crates/components/src/folder_picker.rs` (`FolderPickerModal`) or the "Move to folder" entry in the dots menu in `crates/pages/src/playlists.rs`. I don't have the Rust/Dioxus expertise to debug the UI event wiring myself, so I'm reporting this with what I could gather from the logs. ### Steps to reproduce 1. Open the Playlists page. 2. Create a folder using the folder-plus button in the header. 3. On an existing playlist (outside the folder), open the "…" menu and click "Move to folder". 4. In the popup, click the folder you just created. 5. Observe: the playlist does not move into the folder. 6. Restart the app — the folder is still empty. ### Music source Local library ### Platform Windows desktop ### Kopuz version v0.13.0 ### Logs or console output ```shell create_folder shows up in the log: INFO create_folder{name="新しいフォルダー" id=ca9ec064-a7b6-47dd-8224-aa5976a715a5}: db::backend::writes: close time.busy=278µs time.idle=67.2µs set_playlist_folder never appears anywhere in the log, despite going through the "Move to folder" flow twice. ``` ### Screenshots or recordings _No response_ ### Additional context _No response_