Allow for test continuation even when phase timeout occurs

The current behavior for when a test phase exceeds a configured timeout is that the phase result itself is reported as TIMEOUT and the entire test is aborted. There are instances where one may want to execute subsequent test phases even when a timeout for a previous phase occurs.
Therefore, propose adding a parameter to determine the behavior for a test phase when its timeout is triggered. The default behavior can still be to abort the test, but an option should be added to continue to the next phase. The phase that timed out can still be marked as TIMEOUT.