fix(music): add spotify-tokener with Chromium for Partner API anonymous tokens

Spotify changed their API in Feb 2026 - playlists now require anonymous
tokens via the Partner API. The default anonymous token endpoint is
blocked from server IPs. Added a custom Dockerfile for spotify-tokener
with Chromium installed, and configured LavaSrc to use Partner API with
the tokener endpoint. Playlists now load successfully.

docker-compose.yml

@@ -1,8 +1,19 @@
 services:
+  spotify-tokener:
+    build:
+      context: ./lavalink
+      dockerfile: Dockerfile.tokener
+    container_name: spotify-tokener
+    restart: unless-stopped
+    environment:
+      - SPOTIFY_TOKENER_CHROME_PATH=/usr/bin/chromium
+
   lavalink:
     image: ghcr.io/lavalink-devs/lavalink:4-alpine
     container_name: loki-lavalink
     restart: unless-stopped
+    depends_on:
+      - spotify-tokener
     ports:
       - "127.0.0.1:2333:2333"
     volumes:
@@ -13,7 +24,6 @@ services:
       JAVA_OPTS: "-Xmx1G -Xms256M"
       SPOTIFY_CLIENT_ID: ${SPOTIFY_CLIENT_ID}
       SPOTIFY_CLIENT_SECRET: ${SPOTIFY_CLIENT_SECRET}
-      PLUGINS_LAVASRC_SPOTIFY_PREFERPARTNERAPI: "true"
     healthcheck:
       test: ["CMD-SHELL", "wget -q -O /dev/null --header=Authorization:Hch4HiVCxkKs9JPiSnrt4Q http://localhost:2333/v4/info || exit 1"]
       interval: 30s