Added semicolon test for Java parser

[rlsanders4]

What's changed?

This adds a new unit test to JavaParserTest that validates that the parser is working correctly when a simicolon is specified directly after the final bracket in a method declaration.

What's your motivation?

A semicolon specified in this manner is unnecessary, but it is still valid Java code. The parser is currently unable to parse this, and the unit test gives the following error:

Source file was parsed into an LST that contains non-whitespace characters in its whitespace. This is indicative of a bug in the parser. 
public class Test {
  public static void myMethod() {
  }~~(non-whitespace)~~>;
<~~}

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[timtebeek]

Thanks again for reporting this issue @rlsanders4 ; logging some useful context from Slack here as well:

I believe mapping these semicolons to J.Empty statements would be the correct course of action.