Update GitHub Action Versions

[morisil]

GitHub Actions Version Updates

• actions/setup-java published a new release v5.6.0 on 2026-07-16T14:46:41Z
• anthropics/claude-code-action published a new release v1.0.176 on 2026-07-17T00:27:55Z

[claude]

Review

This is a routine, auto-generated version bump from the action-version-updater.yml workflow (saadmk11/github-actions-version-updater), touching only version pins in three workflow files:

• actions/setup-java@v5.5.0 → v5.6.0 (build-gradle.yml)
• anthropics/claude-code-action@v1.0.175 → v1.0.176 (claude-code-review.yml, claude-code.yml)

Assessment: Low risk, mechanical change. No code logic, only version strings.

• Code quality: Clean, consistent with the pattern already used across these workflows.
• Bugs: None found — the diff is a like-for-like version bump with no other changes to with: blocks or job logic.
• Security: Both are patch/minor bumps from reputable, actively maintained actions (official actions/setup-java and anthropics/claude-code-action). Since these workflows are pinned by version tag rather than commit SHA, there's inherent trust in upstream tag integrity — this is a pre-existing pattern in the repo, not something introduced by this PR, so no new risk here.
• Test coverage: N/A for a version bump; the real verification is that dependent workflows (build-gradle.yml, claude-code.yml, claude-code-review.yml) continue to run successfully after merge.

Minor observation (non-blocking): .github/workflows/reference/build-release.yml still pins actions/setup-java@v5.1.0 and wasn't touched by this update. If that file is an active reusable workflow rather than just a reference/example, it may be worth checking why the updater skipped it (possibly excluded by path, or just picked up on a future run).

No changes requested — looks good to merge.