[AMORO-4384]add jdk version check and add more add-opens

[Aireed]

Why are the changes needed?

Close #4384 .

Brief change log

• add java version check in load-config script and add more extra option dependes on the java version

How was this patch tested?

• Add some test cases that check the changes thoroughly including negative and positive cases if possible

• Add screenshots for manual tests if appropriate

• Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[sivakumar-mahalingam]

Could we use $JAVA_RUN -version instead of java -version? If PATH points to JDK 11 but JAVA_HOME points to JDK 17, the script detects Java 11 while AMS runs on Java 17. Consequently, the required --add-opens option is not added, leaving #4384 unresolved.

[Aireed]

Could we use $JAVA_RUN -version instead of java -version? If PATH points to JDK 11 but JAVA_HOME points to JDK 17, the script detects Java 11 while AMS runs on Java 17. Consequently, the required --add-opens option is not added, leaving #4384 unresolved.

thanks for you advice. nice catch. i have fixed it. PTAL

[sivakumar-mahalingam]

Could we use $JAVA_RUN -version instead of java -version? If PATH points to JDK 11 but JAVA_HOME points to JDK 17, the script detects Java 11 while AMS runs on Java 17. Consequently, the required --add-opens option is not added, leaving #4384 unresolved.

thanks for you advice. nice catch. i have fixed it. PTAL

You are welcome. The fix looks fine. @zhoujinsong please validate

[zhoujinsong]

LGTM.

BTW, I noticed the optimizer.sh script have some similar logic about changing the JVM variables depend on the JDK version.
We may polish the implementation here in another PR.