Update Conda recipe's GLIBC to 2.28

[jakirkham]

RAPIDS dropped CentOS 7 / GLIBC 2.17 support already: #23

Also the CUDA Toolkit deprecated CentOS 7 / GLIBC 2.17 support in CUDA 12.4.0

However we hung onto some references to GLIBC 2.17 in Conda recipes (for example) as there was not a way to update them and there was no pressing need given they would still build ok (albeit with somewhat lax metadata).

Since then conda-forge added support for packages to build with GLIBC 2.28 and 2.34 (based on AlmaLinux 8 and 9 respectively). The default remains to build packages with GLIBC 2.17 compatibility.

While there are several CUDA Toolkit and other CUDA packages that have kept working with GLIBC 2.17, some have already dropped support. Here are a few examples (however there are more):

• cudnn
• libcufile
• libnvtiff

As a result installing newer versions of the CUDA Toolkit or other CUDA packages, will become impossible for newer versions

To address this, would recommend that we update the GLIBC version used in our Conda recipes. Doing this would amount to changing our conda_build_config.yaml's like so

 c_stdlib_version:
-  - "2.17"
+  - "2.17"

[jakirkham]

It may make sense to couple this with the upgrade to GCC 13. They are similar changes in nature and happen in the same file

xref: #129

[bdice]

I implemented PRs for #129 and this issue. Track the status here: #129 (comment)