Enable CUDA 13.0 migrator

[bdice]

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.

Following #7653, we are now ready to begin the CUDA 13.0 migration.

[bdice]

cc: @carterbox @billysuh7 @jakirkham @sisodia1701 for awareness

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

[h-vetinari]

In #7653, @carterbox had a comment

Insert note here about binary path changes on Windows

Is this still relevant?

---

We still have 75 feedstocks to do for the 12.9 migration; not a blocker as I said, but would be good to tackle these (not least because of the wait_for_migrators: here).

[carterbox]

In #7653, @carterbox had a comment

Insert note here about binary path changes on Windows

Is this still relevant?

No. We decided to revert moving CTK DLLs from /bin/*.dll to bin/x64/*.dll in CTK 13.0.1, so end users don't need to know about the move.

We still have 75 feedstocks to do for the 12.9 migration; not a blocker as I said, but would be good to tackle these (not least because of the wait_for_migrators: here).

Is wait_for_migrators per feedstock or channel-wide? What we want is for the CUDA 13.0 migration to start immediately on feedstocks that have already migrated to CUDA 12.9.

[h-vetinari]

Is wait_for_migrators per feedstock or channel-wide? What we want is for the CUDA 13.0 migration to start immediately on feedstocks that have already migrated to CUDA 12.9.

The intention is per-feedstock. But it's a rarely-used piece of infrastructure, so keep an eye out if things aren't working

[bdice]

Thanks @h-vetinari for the questions and feedback! Do you think this is ready to merge, or do you have further questions?