Invalid "selection" values in "read_zarr()" should raise an error

[AlbertoFabbri93]

spatialdata.read_zarr() currently appears to silently ignore invalid values passed to selection.

For example:

sdata = spatialdata.read_zarr(
    path,
    selection=("table",),
)

returns a SpatialData object with no loaded tables instead of indicating that "table" is not a valid selector.

It would be safer if read_zarr() validated selection against the supported values:

{"images", "labels", "points", "shapes", "tables"}

and raised a clear ValueError for unknown entries. Silent failure can otherwise make a valid Zarr store look empty and is difficult to diagnose.

[Tomaz-Vieira]

I actually think the right fix would be to tighten the type of selection to:

Tuple[Literal["images", "labels", "shapes", "points", "tables"], ...] | None

so we can catch these errors statically. If we want to be extremely nice towards people not using a type checker, we could also assert that, since passing anything other than Literal["images", "labels", ...] is a violation of the preconditions of the function, and therefore a bug, not a recoverable exception.