fix(jest-resolve): disable jest-pnp-resolver for Yarn 2

[merceyz]

Summary

In #9520 jest-resolve was switched to use resolve which, because Yarn 2 patches it, supports PnP. This makes jest-pnp-resolver unnecessary but it can't be removed as that would be a breaking change for Yarn 1 PnP users but it can be disabled for Yarn 2.

Main reason for doing this is that jest-pnp-resolver doesn't support projects where there are multiple pnpapi instances but the patch in resolve does.

Test plan

Tests should still pass

[jeysal]

Nothing unusual in the code and given this comes from someone involved in Yarn and Maël has +1ed, I'll just trust the reasoning behind it :D
We also have e2e tests I think soooo...

[SimenB]

Yay! 🎉

The PnP integration test fails on CI, tho.

Also, can you remove https://github.com/facebook/jest/blob/a66eec74b55dc98ab072be330c13c54c35cba5f7/packages/jest-resolve/src/defaultResolver.ts#L26-L33?

[merceyz]

I can't actually remove the plugin as that would be a breaking change for Yarn 1 PnP users, so instead I disabled it for Yarn 2. I updated the test and it passes locally so lets hope the CI agrees

[SimenB]

👍

We could consider dropping v1 support in a future major

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.