Pin cartopy<0.24 on v2.11.x release branch

[valeriupredoi]

Description

Porting #3768 into the release branch so we can extract a build=1

It may be necessary to have other dependencies pinned, that have evolved in the meantime. I will use the lock file for that, and will post the deps that I end up pinning in a comment below, in this PR 🍺

[valeriupredoi]

Updated (pinned) dependencies:

• curl <8.10 # [Julia] pin curl <8.10 to restrict libcurl <8.10 so Julia installs packages correctly #3755
• flake8 <6 # code style not updated to major release 6 (we have 5.0.4 in the lock file) no need to pin flake8, I only had to fix the little mistake in dec9b85

[schlunma]

Great, thanks V! Doc build still fails due to #3762

[valeriupredoi]

Cheers Manu 🍺 yeah we'll have dev docs broken if we rerelease, but i'll just be a rebuild so we should be ok

[bouweandela]

@valeriupredoi @schlunma Why do we need another release just to pin cartopy? Wouldn't it be sufficient to just do a new build of the conda package?

[valeriupredoi]

Yes but I wanted to have it in the release branch too, so we are all covered

[valeriupredoi]

Am not gonna release per se, via the GH/PyPI mechanism, just a rebuild on c-f but wanted to make sure all tests pass etc etc

[bouweandela]

OK, sounds good. I was worried you were planning a new release just for this 🍻

Question answered

[schlunma]

Yes but I wanted to have it in the release branch too, so we are all covered

Yeah, that's what I thought too 👍

[valeriupredoi]

OK, sounds good. I was worried you were planning a new release just for this 🍻

ha no, am just doing things to account for any issues down the line - the lazy way of doing things, so I don't have to work more in case stuff breaks later 😁