Introduce mechanism for terminating Dynamic Tests early

[mmerdes]

Dynamic Tests are non-deterministic in nature. Sometimes it might not be clear to the test author (let alone the IDE) when or even if the execution will terminate.
It has been suggested to introduce a timeout to stop the execution before it would terminate by itself. An alternative would be to terminate the execution when a certain number of failed (or successful tests) have been executed.

[sormuras]

With #838 in the works, it is easy to get and store the initial time instant when a "@testfactory"-annotated methods started. The user-supplied code then could calculate the difference to now and throw an (time out) exception in a "requiredTest" executable. That breaks the execution loop.

Or, a time-out value could be passed at the "@testfactory" annotaion level and the interpreted internally.

[sormuras]

Or the user may supply a predicate object that is asked before every dynamic test execution whether the execution loop should continue or not.