Build for numpy 2.0

[ocefpaf]

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.

I do have some suggestions for making it better though...

For recipe:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[h-vetinari]

If you want, you could copy the migrators touched by conda-forge/conda-forge-pinning-feedstock#5790 into .ci_support/migrations with use_local: true and then rerender. I've done this in conda-forge/pythran-feedstock#84 and a couple other feedstocks, for example. Just if you want though. ;-)

[trexfeathers]

Many thanks @ocefpaf ❤

[ocefpaf]

@trexfeathers note that this is mostly for testing. I sent a PR upstream in SciTools/cf-units#427 and the relevant commit is SciTools/cf-units@7fbaeeb. Feel free to copy that over in a better PR if you want. Mine is a bit messy b/c I really cannot make heads or tails of the CI configuration there.

[trexfeathers]

@ocefpaf OK, appreciate the clarification. Hopefully @bjlittle and @pp-mo (our current cf-units leads) will be able to find some time soon 🤞