Update numpy constraint to >=2.0.0,<=3.0.0

[tomvothecoder]

Description

• Closes [Bug]: conda update wants to downgrade xcdat from 0.7.1 to 0.7.0 #677
• Closes [Bug]: xESMF related issue "AttributeError: np.NaN was removed in the NumPy 2.0 release. Use np.nan instead." #668
• Update sub-dependencies to min version that supports NumPy 2.0

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:

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass with my changes (locally and CI/CD build)
• 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)

[tomvothecoder]

Will need to release a new version of xCDAT for this (v0.7.3)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (96bc649) to head (57c6288).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #711   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           15        15           
  Lines         1555      1555           
=========================================
  Hits          1555      1555           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tomvothecoder]

Hey @xylar, I'm checking in with you to make sure these constraints are fine with E3SM Unified.

In addition to the new numpy constraint, I've constrained other packages to the minimum version that supports numpy 2.0.

[xylar]

Yes, that's great! The only constraint there that clashes with current E3SM-Unified is xarray but you're absolutely right that we're going to have to update that as well to support numpy 2.0.

[tomvothecoder]

Great, thanks for confirming