[ISSUE #10341] Fix Bazel CI build failure caused by Maven Central rate limiting

[lizhimins]

Summary

• Disable fetch_sources to halve Maven download requests and avoid HTTP 429 rate limiting
• Add repo.maven.apache.org as fallback mirror repository
• Add actions/cache for Bazel repository cache to avoid redundant downloads across CI runs
• Upgrade actions/checkout from v2 to v4

Test plan

• Verify Bazel CI workflow passes without 429 errors
• Confirm build and test targets still compile successfully

Closes #10341

🤖 Generated with Claude Code

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.85%. Comparing base (17b4e56) to head (94dbbea).

Additional details and impacted files

@@              Coverage Diff              @@
##             develop   #10342      +/-   ##
=============================================
- Coverage      48.96%   48.85%   -0.12%     
+ Complexity     13470    13440      -30     
=============================================
  Files           1375     1375              
  Lines         100452   100452              
  Branches       12973    12973              
=============================================
- Hits           49188    49071     -117     
- Misses         45270    45375     +105     
- Partials        5994     6006      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.