Use glibc 2.17 again

[h-vetinari]

We hadn't documented in #38 why we moved to 2.28, and I forgot the reason (also, the CI logs are no longer there). So double-check what goes wrong with 2.17.

[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). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

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

[h-vetinari]

@xhochy, I don't remember why you increased the c_stdlib_version in #38, but it seems to work fine with 2.17 as well? Could you PTAL? This would make things a bit easier for pyarrow.

[xhochy]

There was a missing symbol in the sysroot headers that got added after 2.17. Seems like they removed the dependency again.

[xhochy]

This needs a build no bump.

[h-vetinari]

There was a missing symbol in the sysroot headers that got added after 2.17. Seems like they removed the dependency again.

OK cool! Let's merge this to unblock pyarrow and jaxlib. :)