fix(deck.gl-zarr): raise Zarr open failures through onError

[kylebarron]

updateState discarded the _parseZarr() promise with void, so every failure it can produce was swallowed into an unhandled rejection: a mistyped variable, malformed GeoZarr attrs, unnamed array dimensions, an invalid selection, or a rejecting epsgResolver. The layer simply rendered nothing and the carefully written error messages never reached the app.

Route those through Layer.raiseError so they surface via onError, mirroring the COG layers (#652). Rejection values are normalized before use, since a resolver rejecting with a non-Error would otherwise make error.message throw inside the catch handler and produce the same unhandled rejection this is meant to fix.

Surfacing the errors needs a cancellation story that ZarrLayer lacked entirely, so add one: an AbortController in layer state, aborted by a new finalizeState and replaced on every re-parse. Without it, a layer unmounted mid-open would start raising errors the app can no longer act on. The same controller closes a pre-existing race where a slow earlier parse could resolve after a newer one and write its arrays and descriptor over the newer state. Nothing threads the signal into zarrita, so this guards state writes rather than cancelling reads.

Also drops three window.root/window.group/window.meta debugging assignments that were shipping in the parse path.

What I am changing

How I did it

How you can test it

Related Issues

[kylebarron]

We do need to refactor Zarr parsing to emit errors through onError, but for now I just want to finally get the release out #638