In WFARQ-160 we started throwing assertion exceptions for setup tasks to allow for ignoring further configuration and invocation of test methods. We should re-throw other exceptions as well or at least re-throw assertion exceptions.

When an exception is thrown, there should be an attempt to also invoke the tearDown() method of the ServerSetupTask. This may also end in an error and this error should simply be logged, unless it is an java.lang.AssertionError. This this case we should re-throw the error. This should likely also run each tearDown() method before throwing any other error.