fix(ci): disable bazel cache for cpp linting

[slbotbm]

Which issue does this PR close?

Closes #

Rationale

The linting step for cpp was surfacing the following error:

Save cache for disk-true
  Warning: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
      at file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:400:1
      at Generator.next (<anonymous>)
      at fulfilled (file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:4:1)

Save cache for repository
  Warning: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
      at file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:400:1
      at Generator.next (<anonymous>)
      at fulfilled (file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:4:1)

This PR disables bazel's caching for the cpp linting step.

What changed?

setup-bazel step disabled for cpp linting.

Local Execution

• N/A
• Pre-commit hooks ran

AI Usage

If AI tools were used, please answer:

1. Which tools? codex
2. Scope of usage? issue finding
3. How did you verify the generated code works correctly? N/A
4. Can you explain every line of the code if asked? Yes

[github-actions]

Thanks for the pull request. It is now waiting for review, labeled S-waiting-on-review.

You can update that label as the review goes back and forth, with slash commands - each on its own line, in a regular PR comment (not an inline review reply):

• /ready - mark it S-waiting-on-review again, after addressing feedback
• /author - mark it S-waiting-on-author (maintainers, or anyone who has had a PR merged before)
• /request-review @user ... - request reviewers (@user or @org/team)

Commands take up to ~90s to apply. If no reaction (👍 or 😕) appears on your comment, the apply step likely failed - check the repo's Actions tab for the PR Triage Apply run. Commands posted inside a review body (rather than a normal comment) cannot be reacted to, so they stay log-only.

See CONTRIBUTING.md for details.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.79%. Comparing base (cb5d576) to head (c54c1b5).

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #3281      +/-   ##
============================================
- Coverage     73.79%   73.79%   -0.01%     
  Complexity      943      943              
============================================
  Files          1200     1200              
  Lines        109116   109116              
  Branches      86005    86024      +19     
============================================
- Hits          80525    80522       -3     
+ Misses        25865    25845      -20     
- Partials       2726     2749      +23     

Components	Coverage Δ
Rust Core	74.94% <ø> (+<0.01%)	⬆️
Java SDK	58.44% <ø> (ø)
C# SDK	69.13% <ø> (-0.31%)	⬇️
Python SDK	81.43% <ø> (ø)
Node SDK	91.53% <ø> (+0.09%)	⬆️
Go SDK	39.91% <ø> (ø)
see 22 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.