feat: Minstrel no longer talks to Lidarr: its connection, Delete via Lidarr and the unmonitor options are gone, and the track reports are plain quarantine (M502 #5525)

Migration 0091 drops lidarr_config and renames the quarantine tables, types,
indexes and the history column off the Lidarr name. The Integrations Lidarr
card, the Reports "Delete via Lidarr" action, the merge and remove-track
unmonitor options, the Lidarr audit actions and error codes go, on the
server, web and Android. The README describes acquisition as it is now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

internal/db/queries/users.sql

@@ -96,7 +96,7 @@ RETURNING *;
 -- Hard delete with cascade. The schema's ON DELETE CASCADE foreign keys
 -- handle plays/likes/sessions/etc. Caller must enforce the last-admin
 -- guard at the HTTP layer (count admins, refuse if target is the only
--- admin). The lidarr_quarantine, general_likes*, play_events,
+-- admin). The quarantine, general_likes*, play_events,
 -- sessions, and other user-FK tables all have ON DELETE CASCADE so
 -- this is a clean drop.
 DELETE FROM users WHERE id = $1;