build-and-deploy: use hosted runners for wintoast/gcm for ARM64

The wintoast package contains artifacts built using Visual Studio, i.e.
we can use an x86_64 host to build an arm64 package.

The Git Credential Manager package contains artifacts that are
downloaded from that project (i.e. they are not actually built by Git
for Windows), so we can use an x86_64 host to build an arm64 package.

Therefore, let's special-case these two packages.

Signed-off-by: Johannes Schindelin <[email protected]>

Author: dscho

.github/workflows/build-and-deploy.yml

@@ -241,7 +241,14 @@ jobs:
             printf '#!/bin/sh\n\nexec /mingw64/bin/git.exe "$@"\n' >/usr/bin/git
           } &&
 
-          MINGW_ARCHS_TO_BUILD=$(test "$ARCHITECTURE" == "aarch64" && echo "clangarm64" || echo "mingw32 mingw64")
+          MINGW_ARCHS_TO_BUILD=$(
+                    case "$ARCHITECTURE,$PACKAGE_TO_BUILD" in
+                    aarch64,*) echo "clangarm64";;
+                    *,mingw-w64-wintoast) echo "mingw32 mingw64 clangarm64";; # We're (cross-)compiling via Visual Studio
+                    *,mingw-w64-git-credential-manager) echo "mingw32 mingw64 clangarm64";; # We're downloading the pre-built x86 artifacts and using them for all three platforms
+                    *) echo "mingw32 mingw64";;
+                    esac
+          )
 
           cd "/usr/src/$REPO/$PACKAGE_TO_BUILD" &&
           MAKEFLAGS=-j6 PKGEXT='.pkg.tar.xz' MINGW_ARCH=$MINGW_ARCHS_TO_BUILD $MAKEPKG -s --noconfirm &&