chore: change workspace packages pattern

[Andarist]

Description

I've noticed that the currently used pattern was overly greedy and has classified such things as potential packages:

packages/auto-install/test/fixtures/npm
packages/auto-install/test/fixtures/yarn
packages/auto-install/test/fixtures/yarn-bare
packages/json/test/fixtures/named
packages/node-resolve/test/fixtures

Things were working, but including those as workspace packages was not intentional so better to fix that.

[Andarist]

you can actually see how those were incorrectly included here

[Andarist]

I have no idea why there are so many lockfile changes. I've just executed pnpm i after fixing that workspace option - which had to be done, because it affects lockfile. Not sure why any versions here were changed though.

[shellscape]

Good catch 👍

[Andarist]

A little strange situation - some snapshots have failed due to end of line difference (classic crlf vs lf). It works on master though and I haven't touched those files as part of this PR. Any ideas? My guess is that some dependency has changed but I don't know why they have changed in the first place.

[shellscape]

When you changed the scope and removed the (incorrectly) included packages, pnpm recognized that and cleaned up the lockfile. I don't know why your changes are now causing issues in snapshots, because that doesn't happen on other branches.

[Andarist]

I've "fixed" the problem by normalizing yarn-written files on our end (maybe yarn version has changed on CI in the meantime? although can't find any changelog entry in yarn about a change that could affect this).

[shellscape]

This goes back to #69 and your comment about mocking yarn out. I'm OK if we want to put that off to another PR, but let's put a comment above the changed test lines to explain why that's there. Otherwise it's going to look superfluous to someone not aware of this PR.