ci: test and package application builds and draft releases

[ryanbarlow97]

PRs into main run frontend Vitest and backend pytest suites, upload their JUnit reports, build the Next.js frontend, and package UTC DEV-YYYYMMDD-HHmm source and frontend archives with checksums and build provenance. Numeric v* tags must match frontend/package.json and create a draft archive release after the same checks.

The build uses Ubuntu 24.04, Node 22, Python 3.12, and actions with Node.js 24 runtimes. Test fixtures use a shared temporary database module, isolate storage/session lookups, and supply the current catalog, map-list, and kingdom inputs. The frontend archive is built with NEXT_PUBLIC_API_URL=http://127.0.0.1:8000; a deployment needing another URL must build with that configuration.

Validation:

• Frontend: 1,568 passed, one skipped; production build passed.
• Backend on Python 3.12: 1,099 passed, one skipped, 124 subtests passed.
• Local archive integrity and SHA-256 verification passed; the frontend archive contains .next/BUILD_ID and excludes the build cache.
• Actionlint and diff checks passed.
• Hosted CI passed with zero annotations. Tagged draft publication has not been exercised.

Documentation: TF-Minecraft/Docs#5