Drop range related attributes on load

[bouweandela]

Description

Drop value range-related attributes on load because they are very likely to be invalidated by any preprocessor function that is applied afterwards. They are not needed anymore after loading because they have already been interpreted.

This should fix the issue reported in ESMValGroup/ESMValTool#4434

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🧪 The new functionality is relevant and scientifically sound
• 🛠 This pull request has a descriptive title and labels
• 🛠 Code is written according to the code quality guidelines
• 🛠 Unit tests have been added
• 🛠 Changes are backward compatible
• 🛠 The list of authors is up to date
• 🛠 All checks below this pull request were successful

---

To help with the number pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.16%. Comparing base (77013ca) to head (a689714).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3072   +/-   ##
=======================================
  Coverage   96.15%   96.16%           
=======================================
  Files         270      270           
  Lines       15807    15821   +14     
=======================================
+ Hits        15200    15214   +14     
  Misses        607      607           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hb326]

I just tested the recipe with the new GPCP data with this fix, and everything worked fine. Thanks for the fix, @bouweandela!