Harry Simulation test halts the JVM when errors are detected which loose all history in CI

The Harry simulation test has a few issues, but the biggest is it calls System.exit when an error is found… this blocks the JVM from creating a test report and can loose all history needed to reproduce the issue..

1) when the test fails it doesn’t properly show the seed
2) you can’t rerun the test with the same seed without modifying the code
3) if uncaught exceptions are found the test still passes (this is masking TCM issues)