fix(ci): stop pruning /v1/games from the published site

The step existed because ~1M game pages blew the Pages deployment window.
Games now live in game-catalog and the path holds a 357-byte pointer to
it, which this step was deleting — the URL 404s instead of redirecting.

Refs #1

Author: Seungpyo1007

.github/workflows/deploy-pages.yml

@@ -48,18 +48,6 @@ jobs:
         run: |
           mkdir -p _site
           cp -r site/dist/. _site/
-          # Games remain versioned static source data in this repository, but
-          # publishing nearly one million per-record files exceeds the fixed
-          # GitHub Pages deployment window. Keep the public homepage artifact
-          # to the collections it can serve reliably.
-          rm -rf _site/v1/games
-          node <<'NODE'
-          const fs = require("fs");
-          const path = "_site/v1/index.json";
-          const manifest = JSON.parse(fs.readFileSync(path, "utf8"));
-          delete manifest.collections?.games;
-          fs.writeFileSync(path, JSON.stringify(manifest, null, 2) + "\n");
-          NODE
           touch _site/.nojekyll
 
       - uses: actions/upload-pages-artifact@v3