feat: add a --no-game-data pack narrowing

The install manifest marks each game data file "category": "game_data":
a platform entry only game data profile entries read, or a core file its
profile declares game data. Firmware carries no category. Every manifest
says "categorized": true so the installer can refuse an older list.

generate_pack.py --no-game-data cuts those files from the platform list
and the core profiles before the build, names each one with the cores that
read it as game data, and tags the pack _NoGameData through _narrowings.
verify.py and the pack check take the same cut, so --verify-packs and the
report describe the pack the builder wrote. Modes without a platform
(--emulator, --system alone, --from-md5) and --all-variants refuse it.

.github/workflows/deploy-site.yml

@@ -20,6 +20,8 @@ on:
       - "scripts/deterministic_zip.py"
       - "scripts/dumpcatalog.py"
       - "scripts/exporter/baseline.py"
+      - "scripts/exporter/candidates.py"
+      - "scripts/gamedata.py"
       - "scripts/generate_pack.py"
       - "scripts/generate_readme.py"
       - "scripts/generate_site.py"