fix(plugins): keep globe projection when adding a Zarr layer via addZarrLayer (#1470)

addZarrLayerExclusively called ensureMercatorProjection, snapping the map out of
globe whenever a plugin added a Zarr layer through addZarrLayer — while the
Add Data → Zarr panel (same renderer) kept globe. @carbonplan/zarr-layer
reprojects on the GPU and renders projected data correctly in globe, so the
switch was unnecessary and made the two Zarr entry points inconsistent. Remove
it; the COG / cloud-NetCDF / LiDAR deck.gl paths keep their own
ensureMercatorProjection calls.

Fixes #1466

Author: turban

packages/plugins/src/plugins/maplibre-components.ts

@@ -2281,9 +2281,9 @@ async function addZarrLayerExclusively(
     zarrControl.hide();
   }
 
-  // The untiled Zarr renderer draws in Web Mercator; switch off globe first
-  // (matching the COG raster flow) so the layer paints.
-  ensureMercatorProjection(app.getMap?.());
+  // Zarr renders correctly in globe (proj4js reprojects on the GPU), so — unlike the
+  // COG/deck.gl path — do not force Mercator here. This keeps addZarrLayer consistent
+  // with the Add Data → Zarr panel, which never switched projection. See #1466.
 
   const control = zarrControl;
   const headers = options.headers;