bazel 7.2.1

[xhochy]

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.

[xhochy]

@h-vetinari I'll cleanup the patches later today and would skip ppc64le if I don't get it running by the end of the day. If someone really wants it, they need to put in the effort.

[h-vetinari]

That sounds great to me, thanks a lot! Could you perhaps leave a comment in the PR or in the code somewhere what you've learned (or suspect) about the situation on ppc?

[h-vetinari]

Could you leave a comment how this file is supposed to be generated? Also, if easily automatable, perhaps it would be easier to download/generate this json on the fly in the build script, rather than copy it in via a patch.

[xhochy]

I will try to switch to generation in the build script before I merge.