Add win-arm64 build

[finnagin]

Adds a native arm64 windows build.

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.

[conda-forge-webservices]

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.

I do have some suggestions for making it better though...

For recipe:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[finnagin]

@isuruf I was able to run this build successfully locally but I was wondering if you could give me permission to run it on the self-hosted machines to test it there.

[finnagin]

Similar to conda-forge/bzip2-feedstock#20 the workflow has been set to use the fork for conda-incubator/setup-miniconda#342 until that has been merged in order to specify the install directory for the miniconda install.

[finnagin]

@isuruf when running smithy I had to manually change the runs-on option in the actions workflow. Is there a version of smithy I should be using to do the rerender or some other line I need to add to conda-forge.yml besides self-hosted:true?

Edit: This was solved by conda-forge/conda-smithy#1959