Update xarray requirement from <2023 to <2024

[dependabot[bot]]

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

• 83c2919 Add 2023.08.0 whats-new (#8081)
• 4c07a01 Extending the glossary (#7732)
• ab096b0 unpin numpy (#8061)
• 06a756c add design document for "named-array" (#8073)
• 67835ee Bump pypa/gh-action-pypi-publish from 1.8.8 to 1.8.10 (#8068)
• eceec5f Count documentation (#8057)
• 5892464 [pre-commit.ci] pre-commit autoupdate (#8052)
• 0343761 Zarr : Allow setting write_empty_chunks (#8016)
• fb6bbbe sort when encoding coordinates for deterministic outputs (#8034)
• 92c8b33 Reduce pre-commit update frequency to monthly from weekly. (#8033)
• 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 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[bot]]

Codecov Report

Patch coverage has no change and project coverage change: +0.03% :tada:

Comparison is base (6c32425) 78.59% compared to head (46833ed) 78.63%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #156 +/- ## ========================================== + Coverage 78.59% 78.63% +0.03% ========================================== Files 55 55 Lines 3014 3014 ========================================== + Hits 2369 2370 +1 + Misses 645 644 -1 ``` | [Flag](https://app.codecov.io/gh/daq-tools/kotori/pull/156/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=daq-tools) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/daq-tools/kotori/pull/156/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=daq-tools) | `78.63% <ø> (+0.03%)` | :arrow_up: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=daq-tools#carryforward-flags-in-the-pull-request-comment) to find out more. [see 1 file with indirect coverage changes](https://app.codecov.io/gh/daq-tools/kotori/pull/156/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=daq-tools)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.