feat(boot-test): test.yaml unboundPorts for ports opened only when a player connects

Some servers open a published port only once a player connects (through a
proxy, for example), so the boot test's port check can't see it after boot.
A template lists those ports as unboundPorts in its test.yaml, with the
reason. The first template that needs it lists one UDP port, until a real
client confirms how players reach it.

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

schema/test.schema.json

@@ -33,6 +33,11 @@
       "minimum": 10,
       "maximum": 3600
     },
+    "unboundPorts": {
+      "description": "Published ports the server only opens once a player connects, so the boot test doesn't expect them open. Each one exactly as in defaultPorts, with the reason in a comment.",
+      "type": "array",
+      "items": { "type": "string" }
+    },
     "holdSec": {
       "description": "How long the server must stay up after its ready line to pass (default 60). Its published ports are checked after it.",
       "type": "integer",