Ability to run gradle tests with security auditing or any other JVM-level messaging

Leaving as a separate task. I don't see any way of doing this with Gradle test runner as it uses sockets to pass stream outputs (this itself causes security auditing logs, leading to stack overflow).

We'd need to run such corner cases with a different test runner (different task) or even run JUnit core runner directly as a forked Java process.