Go bazelisk not using tools/bazel.cmd on Windows

The Python version will use it... provided I hack up the call to subprocess and pass `shell=True` which is nbd

The go version seems to just ignore it. lmk if there is some other way you're supposed to do a tools/bazel on Windows.

No source file or test is named. Compare the Go launcher’s handling of `tools/bazel` on Windows with the Python version, focusing on the subprocess call and `shell=True` behavior. Done means the Go version invokes `tools/bazel.cmd` on Windows without requiring the reported workaround.

Written by the indexing model from the issue text.