Add universal image loader

[minhtien-trinh]

Features include:

• Dask array conversion for flexible chunking
• VRAM check to ensure memory sufficiency
• Zarr-backed optimization check for efficient handling of large images

This PR is part of the issue from spatialdata.

Note: This is a work in progress; initial testing is complete, but further validation is needed.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 35.87%. Comparing base (47d651d) to head (00d360e).
⚠️ Report is 259 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (47d651d) and HEAD (00d360e). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (47d651d)	HEAD (00d360e)
	2	1

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #234      +/-   ##
==========================================
- Coverage   43.76%   35.87%   -7.90%     
==========================================
  Files          23       22       -1     
  Lines        2367     2149     -218     
==========================================
- Hits         1036      771     -265     
- Misses       1331     1378      +47     

see 6 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lucas-diedrich]

Hi! This PR and its related issue were referenced here.

We also work with large imaging datasets that exceed memory capacity, particularly CZI and whole-slide imaging files. A strategy that has worked well for us is:

1. Lazily loading data in small chunks using a custom image reader wrapped with dask.delayed,
2. Passing the chunks to dask.array (via dask.array.from_delayed), which is memory-mapped and avoids memory overflow,
3. Reassembling the chunks into a dask.array or Image2DModel.

You can find our implementation here.

For TIFF files, tifffile.memmap could potentially be used for lazy loading, as it returns a memory-mapped NumPy array. This approach does not extend to jpeg and png files. Would love to hear your thoughts!

[LucaMarconato]

Large image loading is now generalized in the PR from @lucas-diedrich that we just merged #279. I'll therefore close the current PR. Thanks for the discussion!