feat: per-template metadata — eliminate meta.json merge conflicts

- move each template's metadata to blueprints/<id>/meta.json (442 files, byte-identical roundtrip with the old root meta.json)
- generate the served meta.json at build time into app/public/meta.json (gitignored); pnpm dev/build run the generator first
- CI validates every blueprints/<id>/meta.json via generate-meta.js --check (required fields, id/folder match, logo exists, folder<->meta bidirectionality) and rejects any committed root meta.json
- remove root meta.json, dedupe-and-sort-meta.js and build-scripts/process-meta.js (obsolete)
- update CONTRIBUTING.md, AGENTS.md and README.md

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

blueprints/java/meta.json

@@ -0,0 +1,18 @@
+{
+  "id": "java",
+  "name": "Java Runtime (Multi-Version)",
+  "version": "8-21",
+  "description": "Configurable Java runtime environment supporting versions 8, 11, 16, 17, and 21. Perfect for Minecraft servers, Spring Boot apps, and custom Java applications.",
+  "logo": "java.png",
+  "links": {
+    "github": "https://github.com/pterodactyl/yolks",
+    "website": "https://java.com/",
+    "docs": "https://docs.oracle.com/en/java/"
+  },
+  "tags": [
+    "java",
+    "minecraft",
+    "runtime",
+    "pterodactyl"
+  ]
+}