Incorrect dropping of 'server.jvm.args' meant to be passed to Arquillian

Various testsuite modules define 'server.jvm.args' maven properties, with the expectation that those will be used to set 'server.jvm.args' system properties in the Surefire process that runs tests. Those system properties in turn are used to resolve expressions in various arquillian.xml files, where they become analogues to params to standalone.sh that WildFly Arquillian uses when starting a WildFly server process.

There are cases in the testsuite where the surefire configuration for setting the 'server.jvm.args' system property is ignoring the 'server.jvm.args' maven property and is instead just setting some 'extra' value. The effect is the server isn't started with the full expected set of params and failures can occur or the tests might not be testing what is expected.

For an example of a problem caused by this, see https://wildfly.zulipchat.com/#narrow/stream/174177-ci-servers/topic/IPv6.20failures.20with.20Windows.20.2B.20SE.2017

In that situation the settings that cause the server to listen on ::1 instead of 127.0.0.1 are being dropped.