Add new emulation integration tests

[veni-vidi-vici-dormivi]

I added emulation tests for the new code path also using DataTree. I added also tests to draw realizations for several forcing scenarios at once, which is new compared to the old tests. What is also new is that I actually use scenario data as forcing data while the old tests used dummy data. There is no real advantage of that I think, I just liked the idea of the test being consistent with the verification process. Note that when I draw realizations for ssp585 and ssp126 I also use the parameter set that was calibrated on those two scenarios which is not really necessary. However, this implicitly tests that all parameter sets we created lead to stable emulations.

• Fully documented, including CHANGELOG.rst

[veni-vidi-vici-dormivi]

Okay this would maybe be a good time for #262 respectively #276. If we deprecate the old functions, could we remove the tests without loosing coverage @mathause? It would be nice we could delete the bundle and the old emulation output files from the repo to save some space.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.32%. Comparing base (75d18fe) to head (2352eb3).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #599      +/-   ##
==========================================
+ Coverage   80.18%   80.32%   +0.14%     
==========================================
  Files          49       49              
  Lines        3068     3070       +2     
==========================================
+ Hits         2460     2466       +6     
+ Misses        608      604       -4     

Flag	Coverage Δ
unittests	80.32% <ø> (+0.14%)	⬆️

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.

[mathause]

Super! Yes agree to deprecate the rest - I am not sure what the best approach is, though - maybe a decorator?

[veni-vidi-vici-dormivi]

Yes agree to deprecate the rest - I am not sure what the best approach is, though - maybe a decorator?

Hm as far as is see the decorator needs a new dependency?

[mathause]

Thanks