[Java] Replace if with ? in Generated toIndentedString-methods

[Chrimle]

Refactors all generated Java classes' toIndentedString-method to internally use Ternary Operator for null-checking, instead of a conventional if-statement.
NOTE: This change should make the method smaller, but will be equivalent in terms of functionality and performance.

Example:

Before:

private String toIndentedString(Object o) {
    if (o == null) {
        return "null";
    }
    return o.toString().replace("\n", "\n    ");
}

After:

private String toIndentedString(Object o) {
    return o == null ? "null" : o.toString().replace("\n", "\n    ");
}

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

---

Summary by cubic

Refactor toIndentedString across all Java templates to use a single-line ternary null check and regenerate samples across Java generators. Behavior is unchanged ("null" for null; toString() with newline indentation otherwise).

^{Written for commit 2909915. Summary will update on new commits.}

[Chrimle]

Only ran j* samples so far, will update tomorrow 👍

[Chrimle]

On second thought, wouldn't it just be simpler with ?: syntax instead?

[Chrimle]

To be completely honest, I don't know if these methods should even be kept at all... that's a lot of boilerplate just to make the output prettier...

[cubic-dev-ai]

No issues found across 3000 files

Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.

[Chrimle]

Ready for review, is this something you could review @wing328 ? 🙌

[Chrimle]

or perhaps @jpfinne could have a look?

[wing328]

cc @bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @martin-mfg (2023/08)

[wing328]

cc @cachescrubber (2022/02) @welshm (2022/02) @MelleD (2022/02) @atextor (2022/02) @manedev79 (2022/02) @javisst (2022/02) @borsch (2022/02) @banlevente (2022/02) @Zomzog (2022/09) @martin-mfg (2023/08)

[wing328]

thanks for the PR

i'm ok with using a single-line ternary null check instead.

let's give it a try