BUG: Fix run exports for libtorch and remove magma pinnings - Protobuf 4.25.3

[carterbox]

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:

• It looks like the 'libtorch' output doesn't have any tests.
• 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.
• You're setting a requirement on sysroot_linux- directly; this should now be done by adding a build dependence on {{ stdlib("c") }}, and overriding c_stdlib_version in recipe/conda_build_config.yaml for the respective platform as necessary. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[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:

• It looks like the 'libtorch' output doesn't have any tests.

[carterbox]

NOTE: Rerendering has caused the CUDA 11.2 build to be removed as part of our channel's CUDA 11.2 EOL schedule, but I think all the reviewers of this package be should be aware of that by now.

[hmaarrfk]

can you pull in the important changes from: #230

[hmaarrfk]

should we patch the magma pinning removal?

[carterbox]

can you pull in the important changes from: #230

Done.

should we patch the magma pinning removal?

The only benefit to using upstream run exports is that you don't download the dev files (headers, config) because we split magma into three packages: magma, libmagma, and libmagma_sparse.

[hmaarrfk]

ok lets see if the builds pass for linux

[carterbox]

Thanks, Mark!

[h-vetinari]

Cool, the brought pytorch up-to-date with the latest protobuf migration! 🥳