Remote service failure bricked bazel temporarily

For a few minutes bazel could not build or test because (I believe) bazelisk was checking for the latest version and failing.

```
bazel test -c opt //...
2023/02/15 22:32:02 could not resolve the version 'latest' to an actual version number: unable to determine latest version: could not list Bazel versions in GCS bucket: could not list GCS objects at https://www.googleapis.com/storage/v1/b/bazel/o?delimiter=/: could not fetch https://www.googleapis.com/storage/v1/b/bazel/o?delimiter=/: Get "https://www.googleapis.com/storage/v1/b/bazel/o?delimiter=/": net/http: TLS handshake timeout
```

I did not expect that a GCS issue could prevent me from using Bazel. This github page was also inaccessible at the same time, which complicated me trying to fix the issue.

Platform: Windows 10
I did not have a .bazeliskrc file.

Start with Bazelisk's version-resolution path for the `latest` version and the GCS request shown in the report, then reproduce the TLS timeout on Windows 10 if possible. Done means a temporary GCS or network failure no longer prevents using Bazel, with behavior covered by an appropriate test.

Written by the indexing model from the issue text.