feat(yarn-pnp): adding support for turbo run w/ yarn pnp

[thebanjomatic]

Regarding #693 (comment) I believe this at least partially addresses Issue: #693, but the scope of the issue is unclear.

More specifically this removes the general check for yarn pnp and moves it into the prune command instead as this is the part that likely has remaining issues with pnp since nothing else that I'm aware of needs to know about node_modules.

This PR builds off of #795, as otherwise you can't even run turbo to be able to hit the previous nodeLinker checks.

Let me know if you would like me to change things around so that it is more explicitly enabling for the run task as opposed to enabling for all but prune.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/vercel/turbo-site/8gFsXo25kYxmztMtL4ke9qB7xUJG
✅ Preview: https://turbo-site-git-fork-thebanjomatic-feat-yarn-pnpenable-run.vercel.sh

[thebanjomatic]

I got a CI test failure on windows-latest, re-running seems to have 'fixed' it. The test failure happens for me locally as well, but also shows up in main and when checking out the v1.1.4 tag, so I don't think its new behavior introduced by this change.

[thebanjomatic]

@jaredpalmer / @gsoltis is there any additional testing that needs to be done to be able to move this PR forward?

[vercel]

@thebanjomatic is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[thebanjomatic]

@gsoltis Is there a way we can get a canary release from this PR so that other consumers with yarn 2 PnP repos can test and validate this change? I have verified that its working in my own repos at this point, but I'm given there wasn't any actual code change made on my part to enable this functionality, I can understand there may be some uncertainty around this PR.