Minor auto-refactor code cleanup on a massive scale

[labkey-jeckels]

Rationale

We can cleanup tens of thousands of warnings across our codebase with IntelliJ's autorefactors. In some cases, this adopts newer, leaner syntax. In others, it simply removes code that's not serving any purpose.

Related Pull Requests

• Minor auto-refactor code cleanup on a massive scale platform#6742

Changes

• Auto-refactors
  • Eliminate redundant toString()
  • Eliminate redundant cast
  • Empty JavaDoc annotations
  • Member variable can be final
  • length() and size() -> isEmpty()
  • Add missing @OverRide
  • Class can be static
  • Remove unused imports
  • toArray() passed array length
  • Remove unnecessary semicolon
  • Explicit type syntax can be replaced by <>
  • Redundant access modifiers
  • Remove redundant initializer
  • "".equals() -> isEmpty()
  • StringBuilder can be replaced by String
  • Fix misordered arguments to assertEquals()
  • StringUtils.defaultString() - Objects.toString()
  • Cast can be replaced with pattern variable
  • Collapse identical catch blocks
  • Type may be primitive
• Manual fixups
  • Delete unused GWT code
  • Improve generics
  • new UnexpectedException() -> UnexpectedException.wrap()

[labkey-adam]

I think an assignment got dropped accidentally (InboundSpecimenUpdateService)

[labkey-adam]

Missing assignment here?

[labkey-jeckels]

IntelliJ dropped the assignment with an auto-refactor. Turns out the value wasn't being used. I restore the assignment and moved the validation to happen whether the value was provided as a Date or a String