Add pycuda to linux-aarch64 migration

[dicta]

Checklist

• Used a personal fork of the feedstock to propose changes

[conda-forge-linter]

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.

[isuruf]

We don't build arm cuda packages yet. See conda-forge/cudatoolkit-feedstock#56

[jakirkham]

Right though this is something we are looking to address

[dicta]

Sorry for the noise, then. I wasn't aware that this was hard blocked by something else.

Right though this is something we are looking to address

@jakirkham Is there anything where additonal help would get this unstuck, or is it waiting on something internal? Note that I'm specifically interested in the L4T case, which doesn't appear to be supported even if the linked PR in cudatoolkit-feedstock were to be merged. From the linked PR:

For Jetson/AGX builds that use conda it's recommended to use a selector and omit the CTK from recipes for now. This means users have to ensure they have the correct version of CUDA installed on their system and it doesn't allow for versioning but the currently JetPack for AGX/Jetson only supports CUDA 10.2.

The above language seems to indicate that downstream recipes could be migrated as long as they were only built against CUDA 10.2, i.e., for L4T. Are we just not there yet wrt infrastructure?