feat(test runner): Support for disable bail

[Edgpaez]

As discussed in #2996 and #3012 this PR enables the user to set a disableBail option to collect all tests killing a mutant. Continuation of #3061

Notes on the implementation:

1. Initially only implemented for jest. The rest of the test runners should continue to work without changes
2. We only track the first error message of the first failing test.

To be done:

• enableBail should be deprecated.
• In the integration tests, jest doesn't bail and always report two tests killing a mutant, although I am sure (and the tests confirm) I'm telling Jest to run with bail = true. I am not sure what to do about this or if this is a problem with my implementation.
  [@nicojs]: This is a problem of our jest-runner implementation. Running with bail apparently never worked 🤷‍♀️. I've removed the implementation and mimicked the behavior of reporting the first failing test when bail is enabled.
• merge jasmine2-node-no-mocks into jest-circus
• add disableBail to the RunOptions (for both DryRunOptions and MutantRunOptions)
• Implement disableBail in the cucumber runner
• Implement disableBail in the jasmine runner
• Implement disableBail in the karma runner
• Implement disableBail in the mocha runner

[Edgpaez]

Ok. So I progressed a little:

1. I added the deprecation warning for enableBail option in the jest config
2. I added disableBail to MutantRunOptions making sure it's not a breaking change. Once everything is implemented we can remove the optional. Now it'd be easier for other test runners to add support to disableBail. I did not added it to RunOptions because we were bailing on the DryRun anyway. I didn't see much value in configuring the dryRun not to bail. Mutant coverage would not be affected and it would only make running stryker slower. You think that makes sense? or should I move it to RunOptions?

[Edgpaez]

I've been trying to make jest bail in the integration tests based on config but I haven't succeeded.

Calling jest's runCLI with runInBand: true makes no difference. Neither does passing it in the config option. maxConcurrency=1 and maxWorkers=1 don't seem to make a difference either.

I added a test that should pass if jest bailed on the first fail. It's skipped for now because jest does not bail

[nicojs]

Thanks for your continued work on this. I've started implementing the e2e tests for jest (and prepared it for adding mocha, jasmine, karma and cucumber as well).

Please take a look at my remarks with regards to jest.

[nicojs]

I've opened an issue in jest: jestjs/jest#11766. I'll try to implement programmatical --bail support there.

We've discussed this in the community meetup and decided to investigate in which version of jest the 'monkey patch' was working. If we can't find a version of jest in which it worked, we'll just remove the feature entirely.

We can mimic the behavior of bail by simply only reporting on the first failing test when bail is enabled.