fix(transformer): don't use cache when tsJestConfig is different

[Tommy228]

Summary

When creating two instances of TsJestTransformer with different ts-jest configurations, they will generate the same config set if provided with the same options.

const tr1 = new TsJestTransformer({ isolatedModules: true });
const tr2 = new TsJestTransformer({ isolatedModules: false });

// @ts-expect-error testing purpose
const cs1 = tr1._configsFor({ config: { cwd: process.cwd() }, cacheFS: new Map() } as TransformOptionsTsJest);
// @ts-expect-error testing purpose
const cs2 = tr2._configsFor({ config: { cwd: process.cwd() }, cacheFS: new Map() } as TransformOptionsTsJest);

console.log(cs1 === cs2); // true

This PR aims to fix this by taking into account the provided tsJestConfig when generating the cache key.

Test plan

Tested on a project using ts-jest. Checked with npm run test-examples

Does this PR introduce a breaking change?

• No

Other information

This fix is needed to remove a workaround on my Jest 29 migration PR of jest-preset-angular thymikee/jest-preset-angular#1901

[Tommy228]

I re-ran the CI tests on my repo and they passed, they might be flaky.

[alfaproject]

@ahnpnl usually I wouldn't say anything because we are all busy but we are kind of stuck with our Angular 15 / Jest 29 update for a while so I was wondering if it's ok to do a release with this fix to try and push things forward?

[Tommy228]

I don't get how this is causing performance issue :/ sorry about that