fix(jest-runner): Support Jest v27

[Garethp]

In Jest version 27 they're changing the default test runner to jest-circus instead of jasmine, which means that the global.jasmine variables never get set up. Since we've already implemented perTest coverage for jest-circus, all we need to do is not try to attach a reporter to the globa.jasmine if it doesn't exist.

I don't see any tests for this bit of code already, and I'm not keen on creating a new e2e test for an alpha release of jest. That being said, optional chaining here doesn't change the behavior, so I think this should be a safe fix. What do you think @nicojs

Fixes #2923

[nicojs]

Thanks @Garethp

Did you still want to do the e2e testing in this branch as well?

We currently have an explicit list of defaults defined here:

stryker-js/packages/jest-runner/src/jest-plugins/with-coverage-analysis.ts

Lines 7 to 14 in dc08592

	/**
	* Jest's defaults.
	* @see https://jestjs.io/docs/en/configuration
	*/
	const jestDefaults = Object.freeze({
	testRunner: 'jest-jasmine2',
	testEnvironment: 'jsdom',
	});

Would there be a way to extract the defaults from jest? I can see it is exported from jest here:

https://github.com/facebook/jest/blob/510c8bb40d42095e8a3c78898579b9624e33e432/packages/jest-config/src/index.ts#L22

If we want to get at it, we should try to resolve it from jest. Kind of tricky, but could be done.

The benefit would be that we can choose to not include jasmine explicitly. The idea is that it would still crash if something else is wrong with jasmine, since coverage analysis perTest would be broken.