[CI] Add retry for bazel download

[chaokunyang]

Feature Request

No response

Is your feature request related to a problem? Please describe

https://github.com/apache/fory/actions/runs/23227647845/job/67513805176?pr=3489

WARNING: Download from https://github.com/bazelbuild/rules_kotlin/releases/download/v1.9.6/rules_kotlin-v1.9.6.tar.gz failed: class java.io.IOException GET returned 502 Bad Gateway or Proxy Error
INFO: Repository rules_kotlin+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.cache/bazel/_bazel_runner/8d280d35b2da959da0f37ed0093e86d5/external/bazel_tools/tools/build_defs/repo/http.bzl:392:31: in <toplevel>
ERROR: /home/runner/.cache/bazel/_bazel_runner/8d280d35b2da959da0f37ed0093e86d5/external/bazel_tools/tools/build_defs/repo/http.bzl:137:45: An error occurred during the fetch of repository 'rules_kotlin+':
   Traceback (most recent call last):
	File "/home/runner/.cache/bazel/_bazel_runner/8d280d35b2da959da0f37ed0093e86d5/external/bazel_tools/tools/build_defs/repo/http.bzl", line 137, column 45, in _http_archive_impl
		download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/bazelbuild/rules_kotlin/releases/download/v1.9.6/rules_kotlin-v1.9.6.tar.gz] to /home/runner/.cache/bazel/_bazel_runner/8d280d35b2da959da0f37ed0093e86d5/external/rules_kotlin+/temp16570266519418829330/rules_kotlin-v1.9.6.tar.gz: GET returned 502 Bad Gateway or Proxy Error
ERROR: Analysis of target '//examples/cpp/hello_world:hello_world' failed; build aborted: java.io.IOException: Error downloading [https://github.com/bazelbuild/rules_kotlin/releases/download/v1.9.6/rules_kotlin-v1.9.6.tar.gz] to /home/runner/.cache/bazel/_bazel_runner/8d280d35b2da959da0f37ed0093e86d5/external/rules_kotlin+/temp16570266519418829330/rules_kotlin-v1.9.6.tar.gz: GET returned 502 Bad Gateway or Proxy Error
INFO: Elapsed time: 20.447s, Critical Path: 0.04s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
Error: Process completed with exit code 1.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

[BaldDemian]

Hi @chaokunyang, I am interested in taking on this issue, could you assign this to me?

[BaldDemian]

Saw the failed CI job... But it seems another network issue even before Bazel is installed, should be irrelevant to this PR 🤔

[chaokunyang]

Could you open another pr to fix it?

[BaldDemian]

No problem, I will dig into it

[BaldDemian]

I did some search. It seems that choco doesn't support retry mechanism internally, so one solution is to add manual retry logic around

fory/ci/run_ci.sh

Lines 143 to 148 in 056b94c

	install_bazel_windows() {
	BAZEL_VERSION=$(get_bazel_version)
	choco install bazel --version="${BAZEL_VERSION}" --force
	VERSION=$(bazel version)
	echo "bazel version: $VERSION"
	}

But I also notice there is a GitHub action setting up Bazel: https://github.com/bazel-contrib/setup-bazel. Considering that choco is only used to install Bazel in Fory's CI, maybe we can remove choco and use this GitHub action to set up Bazel across CI? What do you think @chaokunyang

[chaokunyang]

Use github action would be better

[BaldDemian]

It seems that the build-macos-x86_64 (3.13) job now stably fails due to a update on GitHub's macOS runner hours ago: https://github.com/actions/runner-images/releases/tag/macos-15%2F20260317.0278
I will patch the fix for this as well.

[BaldDemian]

Here is the PR #3494