Add cross-compilation for arm64 and aarch64

[shermansiu]

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.

[shermansiu]

@conda-forge-admin, please 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.

[shermansiu]

@conda-forge-admin, please re-render

[shermansiu]

@conda-forge-admin, please rerender

[h-vetinari]

Don't know if you noticed, but you haven't gotten any Linux jobs here yet

[h-vetinari]

Provider is irrelevant for platforms that are being cross compiled (build_platform: has higher precedence, and so this ends up using the providers for linux_64)

[h-vetinari]

Don't know if you noticed, but you haven't gotten any Linux jobs here yet

Hm, you actually do have a job running on main now. Seems like the setup for running on PRs is not working correctly yet. Can you try rebasing #5? I'm on a phone, so can't help this time

[h-vetinari]

Note that you'll have to wait a bit to get some runners. There's a pytorch PR running currently which is using all the GPUs. That's one more reason why you should switch to CPU runners unless actual GPUs are absolutely necessary. It will allow your jobs to be scheduled more quickly.

In general, please be aware that you're using a very rare resource that's needed by other feedstocks as well. In particular, while developing a PR for some change, you should add

build:
  skip: match(python, "!=312")

(or however this is spelled in v1; still don't know it by heart). Once everything is green you can remove the skip to build out all version only once before merging.