Release candidate RC1 esmvalcore=2.8.1rc1

[valeriupredoi]

Checklist

• Used a personal fork of the feedstock to propose changes
  * [ ] Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[valeriupredoi]

@conda-forge-admin, please rerender

[valeriupredoi]

@bouweandela I noticed we have a set of quite restrictive (well, lower bounds) pins for a number of packages from the pytesting zone, and we never bothered plopping those pins in here, shall I bring them in so we are exactly at the same pins as upstream?

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/esmvalcore-feedstock/actions/runs/5025290100.

[bouweandela]

I wouldn't bother unless you run into trouble. By default you'll get the latest of everything anyway.

[valeriupredoi]

I wouldn't bother unless you run into trouble. By default you'll get the latest of everything anyway.

yeh that's what I thought too, but now, as a responsible maintainer of various dubious packages across c-f, I thought I'd be a bit more tidy about that 😁

[valeriupredoi]

huzzah! Tests pass - can I get a review please 🍺 build and test session with platform linux -- Python 3.11.3 🐍

[valeriupredoi]

@bouweandela you a legend, cheers, bud 🍺