Question: Feature request: test isolation and storage engine cache

Is your feature request related to a problem?

We have several tests that write and/or read test datasets using a common name, using open_zarr and to_zarr. Run individually, they work. However, when (e.g.) writing twice, we have errors as the zarr storage is trying to check to see which variables we may have updated, when in fact it is a new dataset.

Describe the solution you'd like

We would like a method to ensure there is no cached state between tests.

Describe alternatives you've considered

If there is an undocumented way to clear cached state, would be grateful for a pointer (and suggest inclusion in the documentation).

Additional context

No response

Start by reproducing the failure with tests that read and write datasets using open_zarr and to_zarr, especially repeated writes with a common name. Trace the storage engine's cached state during the second write; done means tests can use the same dataset name independently without stale cache errors, or the documented cache-clearing method is verified.