Order rebuilt heatmap and cluster layers from the Vector control

Bumps maplibre-gl-vector to 0.10.12, which carries
opengeos/maplibre-gl-vector#67.

A point-renderer switch on a layer owned by the Add Vector Layer control
made the control rebuild its map layers, but it emitted `layerupdated`
before the (async) rebuild replaced `layerIds`. GeoLibre mirrors those ids
into `metadata.nativeLayerIds` and restacks from them, so it kept ids for
layers the map no longer had and never saw the replacements:
getBeforeStyleLayerId could not anchor and syncExternalNativeLayer moved
nothing. A layer set to the heatmap renderer therefore kept whatever
stacking the rebuild appended it with, drawing above layers the panel puts
on top of it. 0.10.12 emits once the rebuild lands, so the ids stay live.

The preceding commits fix the same symptom on the core GeoJSON path, where
the heatmap/cluster/text/label style layers were missing from the ordered
candidate list outright. Both paths are now verified in the browser: with
the upper layer clustered and the lower one switched to heatmap last, the
draw order comes out heatmap -> cluster -> cluster-count -> circle,
matching the layer panel.

Re-checked MAX_VECTOR_BYTES against `src/lib/utils/remote.ts` in the bumped
package as CLAUDE.md requires: still `2 ** 31 - 1`, mirror unchanged.

Author: giswqs

apps/geolibre-desktop/package.json

@@ -94,7 +94,7 @@
     "maplibre-gl-swipe": "^0.11.2",
     "maplibre-gl-time-slider": "^1.8.4",
     "maplibre-gl-usgs-lidar": "^0.11.1",
-    "maplibre-gl-vector": "^0.10.11",
+    "maplibre-gl-vector": "^0.10.12",
     "openai": "^7.3.0",
     "qrcode.react": "^4.2.0",
     "react": "^19.2.8",

package-lock.json

@@ -68,7 +68,7 @@
     "maplibre-gl-swipe": "^0.11.2",
     "maplibre-gl-time-slider": "^1.8.4",
     "maplibre-gl-usgs-lidar": "^0.11.1",
-    "maplibre-gl-vector": "^0.10.11",
+    "maplibre-gl-vector": "^0.10.12",
     "netcdfjs": "^4.0.0",
     "ngeohash": "^0.6.4",
     "open-location-code-typescript": "^1.5.0",