[Feature]: Test dask=2025.1.0 resolves performance issue with large v3 datasets and update constraint (if yes)

[tomvothecoder]

Is your feature request related to a problem?

Related to:

• EAMxx variables #880 (comment)
• xarray.open_mfdataset() and .load() slow or hangs with 4D dataset (76 GB) after upgrading to dask>=2024.12.0  pydata/xarray#9926
• Reintroduce slice fusion dask/dask#11638
• Release 2025.1.0 dask/community#410

xarray.open_mfdataset() + .load(scheduler="sync") hang with some large E3SM v3 datasets. The root cause was identified as being a regression between dask=2024.11.2 and dask=2024.12.0.

Describe the solution you'd like

• Validate dask=2025.1.0 update fixes performance issue using MVCE from here
• Perform complete v3 run with dask=2025.1.0
• Update dask constraint to dask !=2024.12.0,!=2024.12.1 in dev.yml, ci.yml and pyproject.toml
• Inform @xylar on status and if E3SM Unified can update its constraint

Describe alternatives you've considered

No response

Additional context

No response