Migrate linux-aarch64 build from Travis to Azure

[jdblischak]

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.

---

I noticed that the linux-aarch64 builds were being run on Travis. This PR updates these builds to run on Azure so that all the builds are in one place.

xref: #8

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

[ihnorton]

LGTM pending CI

[jdblischak]

Hmmm...fun. I've been having bad luck with PRs this week.

The osx-arm64 builds are all failing, but that has nothing to do with the changes proposed in this PR (the linux-aarch64 builds all passed on Azure).

The osx-arm64 builds passed for commit b9106fa. What's changed? @DimitrisStaratzis I assume this the same error you are troubleshooting in to #22 (comment)

[DimitrisStaratzis]

Hmmm...fun. I've been having bad luck with PRs this week.

The osx-arm64 builds are all failing, but that has nothing to do with the changes proposed in this PR (the linux-aarch64 builds all passed on Azure).

The osx-arm64 builds passed for commit b9106fa. What's changed? @DimitrisStaratzis I assume this the same error you are troubleshooting in to #22 (comment)

Nothing has changed this is weird. #22 does not have to do with CI failures but rather a runtime issue we have in arm Macs

[jdblischak]

PR #24 demonstrates that the failing osx-arm64 builds are unrelated to the changes in this PR