[wildfly-core] Test configuration different to delivered one

common.sh [1] contains server JPMS properties. These properties are used for server start by default in the delivered product.

wildfly-core pom.xml [2] however defines only these properties and not complete set included in common.sh with sun.security.ssl being an unexpected extra:

--add-opens=java.base/java.security=ALL-UNNAMED
--add-opens=java.base/sun.security.ssl=ALL-UNNAMED

Properties above are default properties on both surefire plugin's arg line and for server (through surefire.system.args => jvm.args[3]). Meaning the server instances in testsuite are started with configuration which is different from the user's default configuration. This results in having non-conclusive results for runs on JDK 17.

Another issue is that server and client JPMS properties are coupled and used through one Maven property. This might lead to possible maintenance issues. In the future, server and client properties could be different based on the discussion with bstansbe@redhat.com.

1. https://github.com/wildfly/wildfly-core/blob/main/core-feature-pack/common/src/main/resources/content/bin/common.sh
2. https://github.com/wildfly/wildfly-core/blob/main/pom.xml#L86
3. https://github.com/wildfly/wildfly-core/blob/main/testsuite/standalone/pom.xml#L163