Constrain dask !=2024.12.0,!=2024.12.1 for performance

[tomvothecoder]

Description

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

To do

• Update dask constraint to dask !=2024.12.0,!=2024.12.1 in dev.yml, ci.yml and pyproject.toml
• Validate dask=2025.1.0 update fixes performance issue using MVCE from here
• Perform EAMxx v3 run for ua variable with dask=2025.1.0 -- pending perlmutter back online (2/3/25)
  • auxiliary_tools/cdat_regression_testing/892-bottleneck/run_script.py

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

If applicable:

• New and existing unit tests pass with my changes (locally and CI/CD build)
• I have added tests that prove my fix is effective or that my feature works
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)