Rebuild for cudnn 9.10

[regro-cf-autotick-bot]

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

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:

Conda-forge assumed cudnn 9.x builds would stay compatible with each other.
This is the case for the API/ABI of the library, but nvidia dropped support
for older GPU architectures in cudnn 9.11. Since we have no package-level
metadata about compatibility with specific GPU architectures, this effectively
breaks all packages built atop cudnn for users on affected older GPUs.

In order to remedy this situation, we need to rebuild all cudnn-dependent
feedstocks against cudnn 9.10 (the last version with full architecture support),
before we mark all those newer cudnn builds as broken. This only affects artefacts
for CUDA 12.x; those for CUDA 13.x are not affected, since CUDA 13 never supported
those older architectures in the first place.

For more details see: conda-forge/cudnn-feedstock#124

---

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

[regro-cf-autotick-bot]

Hi! This feedstock was not able to be rerendered after the bot migration changes. I
have pushed the bot migration changes anyways and am trying to rerender again with this
comment. Hopefully you all can fix this!

@conda-forge-admin rerender

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

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

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

[h-vetinari]

Ignoring state of OSX CI here (just timeouts which happen on main as well), because this change is essentially about CUDA