Fix broken $refs from the bambulab schema underscore-rename, remove stale v2/

- print.schema.json, _ams.schema.json, _ams_unit.schema.json still
  pointed at the pre-rename filenames (ams.schema.json, ams_unit.schema.json,
  ams_tray.schema.json) after the underscore-prefix split - fixed all
  three, verified with a full jsonschema + referencing validation run
  against real captures (get_version, pushall, a full print/ams/xcam
  report with both empty and loaded trays) plus negative tests.
- _upgrade_state.schema.json: fixed its $id (pointed at report/info/,
  file lives under report/print/) and its title (said "ModuleInfo",
  clearly copy-pasted from _module_info.schema.json). Wired it into
  print.schema.json as the print report's `upgrade_state` property -
  the file existed but nothing referenced it yet.
- Deleted schemas/bambulab/v2/, which had been recreated as stale,
  broken copies of an older v1 (missing the envelope allOf, missing
  the underscore renames, $ids still pointing at v1/ paths) - the
  repo's own README documents v2 as intentionally removed until V2's
  wire format is known to differ from V1's.
- Updated schemas/bambulab/README.md's layout tree and inheritance-
  example reference, both stale after the underscore rename.
- Removed stray tsc -b build output (packages/ts-types/src/*.d.ts/js)
  that isn't meant to be committed (outDir is dist/, gitignored).

Verified: cargo check clean (continuum-proxy, continuum-ai-worker,
rust-types), tsc clean (continuum-backend, continuum-common ts-core),
10/10 JSON Schema validation cases passing.

schemas/bambulab/v1/report/print/print.schema.json

@@ -2,16 +2,22 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://git.octoturge.com/Continuum/continuum-schemas/raw/branch/main/schemas/bambulab/v1/report/print/print.schema.json",
   "title": "PrintReport",
-  "description": "The ongoing print-state push (root key \"print\") — NOT a direct reply to the pushall request (that goes to \"pushing\", see request/pushing/pushall.schema.json). Sending pushall makes the printer start/refresh this stream; it isn't itself request/response, which is also why this is its own category folder rather than sitting under pushing/ — a category here is 'what root key does this arrive under', not 'what triggered it'. Doesn't extend envelope.schema.json: the example seen so far doesn't show sequence_id/command on this one, and it may genuinely not carry them (an async push, not a direct reply) — revisit if a real capture proves otherwise. The real payload has many more fields than shown here (this example was truncated) — add them under `properties` the same way you'd add them to bambu_commands/print.rs.",
-  "type": "object",
-  "properties": {
-    "ams": { "$ref": "ams.schema.json" },
-    "ams_exist_bits": { "type": "string" },
-    "insert_flag": { "type": "boolean" },
-    "power_on_flag": { "type": "boolean" },
-    "tray_exist_bits": { "type": "string" },
-    "tray_is_bbl_bits": { "type": "string" },
-    "xcam": { "$ref": "xcam.schema.json" },
-    "xcam_status": { "type": "string" }
-  }
+  "description": "The ongoing print-state push (root key \"print\") - NOT a direct reply to the pushall request (that goes to \"pushing\", see request/pushing/pushall.schema.json). Sending pushall makes the printer start/refresh this stream; it isn't itself request/response, which is also why this is its own category folder rather than sitting under pushing/ - a category here is 'what root key does this arrive under', not 'what triggered it'.",
+  "allOf": [
+    { "$ref": "../../../envelope.schema.json" },
+    {
+      "type": "object",
+      "properties": {
+        "ams": { "$ref": "_ams.schema.json" },
+        "ams_exist_bits": { "type": "string" },
+        "insert_flag": { "type": "boolean" },
+        "power_on_flag": { "type": "boolean" },
+        "tray_exist_bits": { "type": "string" },
+        "tray_is_bbl_bits": { "type": "string" },
+        "upgrade_state": { "$ref": "_upgrade_state.schema.json" },
+        "xcam": { "$ref": "_xcam.schema.json" },
+        "xcam_status": { "type": "string" }
+      }
+    }
+  ]
 }