[Feature] Don't apply built-in patches when using node_modules resolver

[orta]

• I'd be willing to implement this feature (contributing guide)
• This feature is important to have in this repository; a contrib plugin wouldn't do

Describe the user story

The patches to my knowledge are to handle pnp, but when resolving node_modules they shouldn't need to be applied

Sometimes to use a TypeScript beta you have to update yarn #2672 because the patches can't be applied due to changes in the TS codebase. This isn't a critical issue as it's normally likely that someone with experience in both TS + yarn can handle the update but the TS website updates pretty early, and I'd love to be able to have other compiler folks updating the TS version and not have to also handle the yarn update process

Describe the solution you'd like

No user settings in my project

Describe the drawbacks of your solution

Perhaps @yarnpkg/plugin-compat noops when node_modules resolver?

Describe alternatives you've considered

An option/env var which suppresses the patches

[arcanis]

Starting from master (3.0-to-be) the builtin patches failing to apply will be a warning rather than an error (#2543). They'll still get applied if possible though, since we want to keep the ability to switch between PnP and nm without changing the lockfile.

[orta]

👍🏻 that works for me

[merceyz]

Perfect, I'll close this then 👍