Pitest uses the default jqwik configuration

[martinmladenov]

PR #181 sets certain configuration options to improve jqwik performance. However, those options don't seem to apply when running Pitest mutants. This should be investigated.

[fm2003]

We should look at the configuration options anyway. The following line does not make sense for normal test runs:

.configurationParameter("jqwik.shrinking.default", "OFF")

Using the shrinker is important to make sure error messages are readable. If we think the shrinker takes too long, we should set this parameter instead: "jqwik.shrinking.bounded.seconds" (the default is 10).

For pitest and meta test runs, it's better if the shrinker is off (because we do not display the error messages in those cases). Therefore, we should make sure we can change the configuration depending on the type of test run.

As for this one:

.configurationParameter("jqwik.tries.default", "100")

It would be nice to have a few more tries if we can afford this without reaching time-outs, because the tests are sometimes flaky (whereas they aren't with the default of 1000). Most reference solutions for the PBT assignments take 2 seconds for "Only tests" and around 10 seconds for "Assess", so it seems like we have some room to increase the number of tries (for both normal test runs and pitest / meta test runs).