enforce if brackets with checkstyle

[samfreund]

Description

What changed?

We enforce brackets for if statements now using checkStyle.

Why?

if statements without brackets can easily lead to mistakes and confusion.

Testing

• I have tested this change locally

---

AI Disclosure

• This PR was authored entirely by me
• This PR includes AI-generated code (e.g., from GitHub Copilot, ChatGPT)
  • If yes, I have reviewed all AI-generated code for correctness
  • If yes, please describe which parts were AI-assisted:

Describe AI involvement here if applicable

Ngl, I didn't change all the brackets by hand

---

Merge Checklist

• PR title is a short, imperative summary of changes
• PR description documents the what and why

Additional Checks (if applicable)

• User-facing changes? User documentation is updated
• Breaking changes? Migration guide is included in description and migrations are marked with // MIGRATION: <dataYear> where <dataYear> is the last season the pre-migration data was used in
• Bug fix? Regression test is added
• New dependency? License compatibility is verified and steps have been taken to follow it
• Serde changes? All messages are regenerated with no unexpected hash changes
• Configuration changes? Changes are backwards compatible with previous season's last release
• Pipeline/data exchange changes? Frontend types are updated in ./photon-client/src/types

[spacey-sooty]

I don't like stopping this as one liner early returns are more readable IMO

[thatcomputerguy0101]

I agree that conditional return/break/continue statements are better on a single line.