fix: replace Unrecognized VM option MaxPermSize with MaxMetaspaceSize (#3759)

replace Unrecognized VM option MaxPermSize with MaxMetaspaceSize and upgrade openmldb-batchjob maven.compiler.source and maven.compiler.target to 1.8

Co-authored-by: yangwucheng <[email protected]>

Author: yangwucheng

java/openmldb-batchjob/pom.xml

@@ -16,8 +16,8 @@
 
   <properties>
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-    <maven.compiler.source>1.7</maven.compiler.source>
-    <maven.compiler.target>1.7</maven.compiler.target>
+    <maven.compiler.source>1.8</maven.compiler.source>
+    <maven.compiler.target>1.8</maven.compiler.target>
 
     <spark.scope>provided</spark.scope>
   </properties>

java/pom.xml

@@ -294,7 +294,7 @@
                     <reportsDirectory>${project.build.directory}/surefire-reports</reportsDirectory>
                     <junitxml>.</junitxml>
                     <filereports>WDF TestSuite.txt</filereports>
-                    <argLine>-Xmx8192m -XX:MaxPermSize=2048m -Duser.timezone=GMT+8</argLine>
+                    <argLine>-Xmx8192m -XX:MaxMetaspaceSize=2048m -Duser.timezone=GMT+8</argLine>
                     <skipTests>${scalatest.skip}</skipTests>
                     <systemProperties>
                         <property>