Explicitly allow setting the SecurityManager in tests

java.lang.SecurityManager has been deprecated and marked for removal. While Java
17 JDKs displayed only a warning when setting the SecurityManager, Java 21 JDKs
will throw an UnsupportedOperationException. This can be prevented by setting
the system property java.security.manager.allow to true. Only when issue
https://bugs.openjdk.org/browse/JDK-8199704 has been addressed, we have the
possibility to address this and remove the use of the SecurityManager.

Author: atextor

tools/samm-cli/pom.xml

@@ -169,7 +169,7 @@
                </systemPropertyVariables>
                <forkCount>1</forkCount>
                <reuseForks>false</reuseForks>
-               <argLine>-Xmx6g</argLine>
+               <argLine>-Xmx6g -Djava.security.manager=allow</argLine>
                <skip>${skip.maven.surefire}</skip>
                <reportsDirectory>${project.build.directory}/${testreports.surefire}</reportsDirectory>
                <!-- Do NOT wildcard include *Test.java, because then we would also run the SammCliIntegrationTest -->