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/dbtest/reset.go

@@ -53,8 +53,8 @@ var dataTables = []string{
 	"skip_events",
 	"play_sessions",
 	"sessions",
-	"lidarr_quarantine_actions",
-	"lidarr_quarantine",
+	"quarantine_actions",
+	"quarantine",
 	// #2374. Keyed by (user_id, candidate_mbid) with no FK to artists —
 	// candidates are out-of-library — so the CASCADE from artists/users
 	// does NOT reach it for a leftover row whose user survived. Truncate
@@ -108,7 +108,7 @@ var dataTables = []string{
 	"mb_artist_release_groups",      // M502 #5519
 	"mb_release_groups",             // M502 #5519
 	"mb_artists",                    // M502 #5519
-	"requests",                      // M502 #5520 (was lidarr_requests)
+	"requests",                      // M502 #5520
 	"download_interventions",        // M502 #5523
 	"library_album_matches",         // #5569
 	"release_blocks",                // M502 #5521