Run mvn formatter:format for better Java code format

[wing328]

PR checklist

• Read the contribution guildelines.
• Ran the shell/batch script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates)
• Filed the PR against the correct branch: master for non-breaking changes and 2.3.0 branch for breaking (non-backward compatible) changes.

Description of the PR

For #4295

[ePaul]

I'm not sure if this is feasible on a project of the change frequency like this one ... you get conflicts before a review (or even the CI build) is possible. Though 👍 for the idea.

[wing328]

Yup, closing this one as this will result in a lot of merge conflicts. We'll try to merge more outstanding PRs into master/2.3.0 before running mvn formatter:format again.