Categories from the inner name, spots and groups; fix the name rules

Migration 1200 passed regexes with `?` through knex, which made them
bindings: the live function held blu-$1ray, web-$2dl and h\.$326[45], so
BluRay, WEB-DL and H.264 names without a resolution were Misc. 93% of
recent releases were Misc, as the category came from the name alone.

category becomes a plain column (DROP EXPRESSION, no rewrite) set by a
trigger: the name's category (fixed, no `?` anywhere; adds XXX,
audiobooks, console and PC games, and TV codes like S01e07[ and
S04E01E02), else the prober's inner name's, else one given before (a
spot's), else the groups'. The spot inspector sets a spot's category
(spot_category) on Misc releases it links and on its own releases. The
Newznab and web category lists gain Console, PC Games, Audiobook, Anime,
XXX and Comics. releases:recategorize recomputes existing rows in id
batches, writing only changed rows and waiting under a free-space floor.

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

tests/functional/spots.spec.ts

@@ -102,6 +102,8 @@ test.group('Spots', (group) => {
     assert.isTrue(await inspector.standalone(SPOT))
     const release = await db.from('releases').where('source', 'spot').firstOrFail()
     assert.equal(release.name, 'Lonely File')
+    // Its title says nothing: the spot's category (01, a09: a movie, x264).
+    assert.equal(release.category, 2040)
     assert.equal(release.files, 1)
     assert.isNotNull(release.poster)
     assert.isNotNull(await db.from('posters').where('poster', release.poster).first())