Update xarray requirement from <2024 to <2025

[dependabot]

Updates the requirements on xarray to permit the latest version.

Changelog

Sourced from xarray's changelog.

How to issue an xarray release in 16 easy steps

Time required: about an hour.

These instructions assume that upstream refers to the main repository:

$ git remote -v
{...}
upstream        https://github.com/pydata/xarray (fetch)
upstream        https://github.com/pydata/xarray (push)

1. Ensure your main branch is synced to upstream:

   git switch main
   git pull upstream main

2. Add a list of contributors. First fetch all previous release tags so we can see the version number of the last release was:

   git fetch upstream --tags

   This will return a list of all the contributors since the last release:

   git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | perl -pe 's/\n/$1, /'

   This will return the total number of contributors:

   git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | wc -l

3. Write a release summary: ~50 words describing the high level features. This will be used in the release emails, tweets, GitHub release notes, etc.
4. Look over whats-new.rst and the docs. Make sure "What's New" is complete (check the date!) and add the release summary at the top. Things to watch out for:
   • Important new features should be highlighted towards the top.
   • Function/method references should include links to the API docs.
   • Sometimes notes get added in the wrong section of whats-new, typically due to a bad merge. Check for these before a release by using git diff, e.g., git diff v{YYYY.MM.X-1} whats-new.rst where {YYYY.MM.X-1} is the previous release.
5. Open a PR with the release summary and whatsnew changes; in particular the release headline should get feedback from the team on what's important to include.
6. After merging, again ensure your main branch is synced to upstream:

   git pull upstream main

... (truncated)

Commits

• 15fb1d8 whatsnew for v2024.01.1
• d34ebff implement isnull using full_like instead of zeros_like (#7395)
• 0475435 Fixed typo in custom backend registration documentation (#8645)
• 0a61f0e Pin sphinx-book-theme to 1.0.1 to try to deal with #8619 (#8632)
• 4bb5175 infer_freq: return 'YE' (#8629 follow-up) (#8642)
• 4b5c87b Use ddof in numbagg>=0.7.0 for aggregations (#8624)
• f07e895 xfail zarr test on Windows (#8643)
• d6deb46 Pandas 2.2.0 test fixes (#8638)
• 5a92d48 rename "Y" freq string to "YE" (pandas parity) (#8629)
• e571d1c Use T_DataArray in Weighted (#8630)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7a2752c) 83.36% compared to head (53671a4) 83.36%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #48   +/-   ##
=======================================
  Coverage   83.36%   83.36%           
=======================================
  Files          27       27           
  Lines         944      944           
=======================================
  Hits          787      787           
  Misses        157      157           

Flag	Coverage Δ
unittests	83.36% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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