[CI] Cache Bazel binary in Python CI workflow

[urlyy]

Feature Request

The Python CI workflow sometimes experiences flaky failures. PR #2733 added retry logic to mitigate the issue, but the root cause is that the workflow downloads Bazel on every run.

We should use GitHub Actions caching to avoid downloading Bazel on every run.

Is your feature request related to a problem? Please describe

#2731

Describe the solution you'd like

• GitHub Actions cache is Simple, caches the binary directly.
• Bazelisk can auto-manages Bazel versions with caching.

But I think Fory doesn’t seem to need managing multiple Bazel versions — caching the binary directly is enough. What's your opinion? @chaokunyang

[urlyy]

@SanyamSuyal Are you still willing to continue working on this issue?

[SanyamSuyal]

@urlyy Sure!!

[chaokunyang]

@SanyamSuyal It seems bazel install still take 2 minutes, see more details in https://github.com/apache/fory/issues/2880. Would you like to work on it?

[SanyamSuyal]

@SanyamSuyal It seems bazel install still take 2 minutes, see more details in #2880. Would you like to work on it?

Sure!