Fail after too many additional attempts to evaluate a property

[jcornaz]

Some generator configurations (when using sets, maps or filter), or usage of features like skip or ensureAtLeastOne, might require to generate impossible inputs and lead to a situation where the test is hanging forever.

It is not a huge problem per say, since I believe that the test engine, or eventually the build system, should be responsible for failing after a too long period of time (timeout).

However, Kwik could feature a mechanism that fail faster if the likeliness of being able to generate an input is too low.

For instance the test could fail if more than 10'000 inputs had to be rejected.

It should be of course configurable. System property sound like a good way to configure it.