feat: a wanted list — follow artists on release-type profiles; requests and re-acquisition become wants (M502 #5520)

Minstrel keeps its own list of what it is to get, keyed by MusicBrainz
release group. A want comes from an approved request, a new release by a
followed artist, or an album whose files went missing, and is held once the
library has a full edition of it.

- Migration 0081: release_type_profiles (Standard seeded: Album, EP,
  Single, studio only), follows, follow_seen_groups and wants.
  lidarr_requests becomes requests with plain *_mbid columns; approved
  album and track requests move onto the wanted list, approved artist
  requests become follows, and the library's album artists start out
  followed. missing_reacquisitions and the retry settings go.
- internal/wanted: follows are checked against MusicBrainz discographies
  daily. The first check sets a baseline, and only releases after it are
  wanted unless the follow asked for what already exists. Profiles filter
  by primary and secondary type, so live recordings stay out unless a
  profile ticks Live.
- internal/requests (was lidarrrequests): approving puts the request on
  the wanted list, and an artist request can be approved on a chosen
  profile. A request completes when its want is held.
- The re-acquisition sweeper wants a missing album back instead of asking
  Lidarr; searching for it is the search schedule's (#5521).
- Web: an admin Wanted page (Wanted, Missing files, Held, Following), a
  follow control on artist pages, a release-type profiles card on
  Integrations, "Approve on a profile" on Requests, and want state on
  Missing files. The artist detail API returns the artist's MBID.
- Android: the request body sends artist_mbid, album_mbid and track_mbid.

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

internal/db/queries/users.sql

@@ -174,16 +174,3 @@ SELECT u.id, u.timezone FROM users u
       WHERE pe.user_id = u.id
         AND pe.started_at > now() - INTERVAL '7 days'
    );
-
--- name: GetOldestAdmin :one
--- The account a system-initiated action is attributed to (milestone #290).
--- lidarr_requests.user_id is NOT NULL and a re-acquisition has no requesting
--- human, so the row is owned by the longest-standing admin: it keeps the
--- request auditable and puts it in the same admin queue as everything else,
--- without inventing a synthetic principal the rest of the schema would have
--- to understand. Ordered by id as a tiebreak so the choice is stable across
--- calls rather than depending on scan order.
-SELECT * FROM users
- WHERE is_admin = true
- ORDER BY created_at, id
- LIMIT 1;