Build Python 3.14 with zlib-ng on all platforms

[hmaarrfk]

I really don't believe in fully ripping out zlib from conda-forge.

I think that a targeted approach is much better.

These patches are pretty close to something we could upstream.

xref: conda-forge/conda-forge.github.io#2638

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• 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-admin]

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/meta.yaml) and found it was in an excellent condition.

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

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/19004666526. Examine the logs at this URL for more detail.}

[isuruf]

I'd rather we build zlib-ng in compat mode and not carry these patches.

[mgorny]

Suddenly forcing zlib-ng on all Python users is bound to cause multiple regressions with no clear way back, short of pinning to an older Python 3.14 version.

[hmaarrfk]

pinning to an older Python 3.14 version.

This sounds like a very clear way for me.

Backends, and swaps, and build numbers are actually quite confusing for end users.