Check the photoreal paths in the browser on a synthetic 3D Tiles set

A generated tileset (a plate at ellipsoid level, 50 m and 200 m blocks and
a pitched roof, 27 KB) replaces Google's tiles when a QA page passes
?qaTileset=/path; only a root-relative path on the page origin is
accepted, and the Google credit is not shown for it. The strict harness
serves the set from disk, so nothing reaches Google.

qa-tiles-fixture checks on both engines that sampleHeight reads the block
at 50 m, clampToHeight lands on the roof, tiles and terrain drapes draw
where they should, tilesLoaded turns true, surface points land on the
roof within their budget, and pick renders per pass stay within it.

scripts/package-boundaries.json

@@ -2286,7 +2286,9 @@
       "src/i18n/locales/uk.json",
       "src/i18n/locales/zh-CN.json",
       "src/i18n/locales/zh-Hant.json",
-      "src/globe/contract.js"
+      "src/globe/contract.js",
+      "src/globe/cesium/qaTileset.js",
+      "src/maps/qaTileset.js"
     ],
     "external": ["cesium"]
   },
@@ -3593,7 +3595,9 @@
       "src/globe/cesium/orbital.js",
       "src/globe/cesium/worldTime.js",
       "src/data/geoImportLimits.js",
-      "src/data/geoImportPlan.js"
+      "src/data/geoImportPlan.js",
+      "src/globe/cesium/qaTileset.js",
+      "src/maps/qaTileset.js"
     ],
     "external": [
       "hls.js",