Rebuild for CUDA 12 + PyTorch 2.4

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update cuda120.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

Here are some more details about this specific migrator:

The transition to CUDA 12 SDK includes new packages for all CUDA libraries and
build tools. Notably, the cudatoolkit package no longer exists, and packages
should depend directly on the specific CUDA libraries (libcublas, libcusolver,
etc) as needed. For an in-depth overview of the changes and to report problems
see this issue.
Please feel free to raise any issues encountered there. Thank you! 🙏

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/10481143886 - please use this URL for debugging.}

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

[jakirkham]

Seeing the following error on CI:

Encountered problems while solving:
  - package cuda-version-12.0.0-hd8ed1ab_0 has constraint cudatoolkit 12.0|12.0.* conflicting with cudatoolkit-10.0.130-h8c5a6a4_10

Could not solve for environment specs
The following packages are incompatible
├─ cuda-version >=12.0,<13  is installable with the potential options
│  ├─ cuda-version [12.0|12.0.0] would require
│  │  └─ cudatoolkit 12.0|12.0.* , which can be installed;
│  ├─ cuda-version 12.1 would require
│  │  └─ cudatoolkit 12.1|12.1.* , which can be installed;
│  ├─ cuda-version 12.2 would require
│  │  └─ cudatoolkit 12.2|12.2.* , which can be installed;
│  ├─ cuda-version 12.3 would require
│  │  └─ cudatoolkit 12.3|12.3.* , which can be installed;
│  ├─ cuda-version 12.4 would require
│  │  └─ cudatoolkit 12.4|12.4.* , which can be installed;
│  ├─ cuda-version 12.5 would require
│  │  └─ cudatoolkit 12.5|12.5.* , which can be installed;
│  └─ cuda-version 12.6 would require
│     └─ cudatoolkit 12.6|12.6.* , which can be installed;
└─ cudatoolkit is not installable because it conflicts with any installable versions previously reported.

Would drop these lines as cudatoolkit is only for CUDA pre-12. Starting with CUDA 12 it no longer exists. With CUDA 11 cudatoolkit does exist, however the CUDA 11 compiler adds cudatoolkit as a dependency automatically. So there is no need to add cudatoolkit explicitly

aihwkit-gpu-feedstock/recipe/meta.yaml

Line 41 in 3c2f64d

- cudatoolkit # [cuda_compiler_version != 'None']

aihwkit-gpu-feedstock/recipe/meta.yaml

Line 53 in 3c2f64d

- cudatoolkit # [cuda_compiler_version != 'None']

That should fix CI

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

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

For recipe/meta.yaml:

• No valid build backend found for Python recipe for package aihwkit-gpu using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[jakirkham]

@conda-forge-admin , please re-render

[jakirkham]

Looks like the build needs cuBLAS

  /home/conda/feedstock_root/build_artifacts/aihwkit-gpu_1724992663380/work/src/rpucuda/cuda/cuda_util.h:24:10: fatal error: cublas_v2.h: No such file or directory
     24 | #include "cublas_v2.h"
        |          ^~~~~~~~~~~~~

[jakirkham]

Added based on these #includes

[jakirkham]

Needed due to ATen usage, which comes from PyTorch that in turn needs cuSPARSE

[jakirkham]

Another ATen dependency

[jakirkham]

This is passing! 🥳

@kkvtran could you please review? 🙂

Also if it looks good, please feel free to merge