fix: Skip previous encoding workaround for fixed xarray versions

[coroa]

Follow up to a workaround introduced by @euronion in #236 for an encoding issue in xarray (pydata/xarray#7691), which was fixed by (pydata/xarray#8713) and eventually included xarray v2024.03.0 (https://github.com/pydata/xarray/releases/tag/v2024.03.0).

Checklist

• Code changes are sufficiently documented; i.e. new functions contain docstrings and further explanations may be given in doc.
• Unit tests for new features were added (if applicable).
• Newly introduced dependencies are added to environment.yaml, environment_docs.yaml and setup.py (if applicable).
• A note for the release notes doc/release_notes.rst of the upcoming release is included.
• I consent to the release of this PR's code under the MIT license.

[lkstrp]

We could also just pin xarray now

[coroa]

We could also just pin xarray now

I guess with all the changes xarray is undergoing, having a half-year old version as lower bound is quite acceptable, true.

[euronion]

Thanks for the cleanup. I'm also in favour of restricting the xarray version. Btw. did you test whether the fix in xarray actually worked? I never got to testing it...

[coroa]

Thanks for the cleanup. I'm also in favour of restricting the xarray version. Btw. did you test whether the fix in xarray actually worked? I never got to testing it...

The dataarrays we receive from CDS has in xarray an encoding of float32 now. As far as i understand that means the fix is working.

[coroa]

Ok, i replaced the implementation by a new version pin.