fix(ci): propagate failures from multi-project hooks

[Standing-Man]

Which issue does this PR address?

Closes #
Relates to #

Rationale

The Java, Go, and Node hooks executed multiple projects in shell loops without fail-fast behavior. When an earlier project failed but a later project passed, the loop returned a successful exit status and allowed the commit or push to continue.

What changed?

• make java-gradle-check stop on the first Gradle failure
• make go-fmt stop on the first formatting failure
• make go-mod-tidy stop when go mod tidy changes files or fails
• make node-eslint stop on the first dependency installation or lint failure
• replace conditional && loop bodies with explicit if blocks
• enable bash -e for all affected hooks

Local Execution

• Passed / not passed
  Passed
• Pre-commit hooks ran / not ran
  Ran

AI Usage

[github-actions]

Thanks for the PR. It is labeled S-waiting-on-review and queued for review.

Slash commands (own line, regular comment) move it around the queue:

• /ready - back to S-waiting-on-review after addressing feedback
• /author - flip to S-waiting-on-author while you finish changes
• /request-review @user-or-team - request a reviewer

See CONTRIBUTING.md for details.