[Java17] Add --add-export settings to restore JDK17 compatibility

After #13700 updated google-java-format dependency, it is now required to add a number
of `--add-export` flags in order to run on JDK17. This commit adds these flags to the
jvm options for a running logstash, and to the tests running on gradle to enable tests
to still work

Author: robbavey

build.gradle

@@ -83,6 +83,13 @@ allprojects {
 
   //https://stackoverflow.com/questions/3963708/gradle-how-to-display-test-results-in-the-console-in-real-time
   tasks.withType(Test) {
+    jvmArgs = [
+      "--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED",
+      "--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED",
+      "--add-exports=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED",
+      "--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED",
+      "--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED"
+    ]
     testLogging {
       // set options for log level LIFECYCLE
       events "passed", "skipped", "failed", "standardOut"
@@ -893,4 +900,4 @@ if (System.getenv('OSS') != 'true') {
  tasks.register("runXPackIntegrationTests"){
      dependsOn copyPluginTestAlias
      dependsOn ":logstash-xpack:rubyIntegrationTests"
- }
+ }

config/jvm.options

@@ -73,6 +73,12 @@
 # Copy the logging context from parent threads to children
 -Dlog4j2.isThreadContextMapInheritable=true
 
+11-:--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED
+11-:--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
+11-:--add-exports=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED
+11-:--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED
+11-:--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED
+
 11-:--add-opens=java.base/java.security=ALL-UNNAMED
 11-:--add-opens=java.base/java.io=ALL-UNNAMED
 11-:--add-opens=java.base/java.nio.channels=ALL-UNNAMED