[23.x] Upgrade to CUDA 13.0

[regro-cf-autotick-bot]

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

IMPORTANT: If you close this PR, the bot will presume that the feedstock has been rebuilt with this update and WILL NOT MAKE ANOTHER PR. Please follow the instructions below for handling this PR.

Notes and instructions for handling this PR:

• If your package IS COMPATIBLE with this update and...
  • the tests have passed, please merge this PR!
  • the tests have not passed, please make changes
    and/or rerun the tests so that they pass. Feel
    free to push to the bot's branch to
    update this PR if needed. Then merge the PR once
    the tests pass!
  • you find it easier to do the update in another PR,
    please do not close this PR until the other PR is merged.
• If your package IS NOT YET COMPATIBLE with this update,
  please leave this PR open. The bot will detect conflicts
  and remake the PR as new versions are pushed. Once the package
  is at a compatible version, please merge the update PR for that
  version.
• If your package WILL NEVER BE COMPATIBLE with this update,
  please convert this PR to draft.
• If this PR HAS CONFLICTS and...
  • you do NOT want to resolve them yourself, add a
    bot-rerun label and the bot will do it for you.
    See the instructions below if you
    do not have permissions to add a label.
  • you do want to resolve them yourself, by all means
    go ahead (either in the UI or via the git CLI)!

---

Here are some more details about this specific migrator:

CUDA 13.0 requires architecture sm_75 or higher, and renamed sm_101 to
sm_110. To build for these, maintainers will need to modify their existing list of
specified architectures (e.g. CMAKE_CUDA_ARCHITECTURES, TORCH_CUDA_ARCH_LIST, etc.)
for their package.

Since CUDA 12.8, the conda-forge nvcc package now sets CUDAARCHS and
in its activation script to a string containing all
of the supported real architectures plus the virtual architecture of the
latest. Recipes for packages who use these variables to control their build
but do not want to build for all supported architectures will need to override
these variables in their build script.

ref: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#new-features

[[!IMPORTANT]]
Remember to update any CUDA 11/12 specific selector syntax in the recipe to include
CUDA 13. For example # [(cuda_compiler_version or "None").startswith("12")]
might be replaced with # [cuda_compiler_version != "None"].

---

This package has the following downstream children:

• pyarrow
  and potentially more.

---

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/24888569933 - please use this URL for debugging.}

[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/24890146907. Examine the logs at this URL for more detail.}