Bazelisk pulls incorrect Bazel on Windows ARM64

[jxy-s]

The x64 version of bazelisk is compatible with a Windows ARM64 machine, it will run under x64 emulation on Windows. However it ends up pulling the x64 version of Bazel which causes unintended downstream behavior.

• toolchains are not resolved as expected
• the host OS is not reflected correctly causing the default compilation to produce an x64 binary instead of an ARM64 one

Bazelisk should pull the ARM64 version of when running on Windows ARM64 instead of the x64 version.

See: bazelbuild/bazel#22164 (comment)

[meteorcloudy]

This is probably because we don't have windows arm64 binary for bazelisk itself. @fweikert Do you know how hard it would be to add? We cross-compile all binaries with the go toolchain anyway, right?

[meteorcloudy]

Maybe it's as simple as adding another target for windows arm64 here?

bazelisk/BUILD

Lines 145 to 153 in 47f6047

	go_binary(
	name = "bazelisk-windows-amd64",
	out = "bazelisk-windows_amd64.exe",
	embed = [":go_default_library"],
	goarch = "amd64",
	goos = "windows",
	pure = "on",
	visibility = ["//visibility:public"],
	)

[albertocavalcante]

@meteorcloudy my understanding is the same. I will try to submit a PR for this.