fix(pnp): skip uninstalled unrelated packages when looking up binaries

[cdcxd]

What's the problem this PR addresses?

Closes #7264

...

How did you fix it?

I made pnp linker follow the same thing done for node modules linker:

berry/packages/plugin-nm/sources/NodeModulesLinker.ts

Line 76 in 57081c0

(err as any).code = `LOCATOR_NOT_INSTALLED`;

That signal the package can't be located and allows it to skip (already in

berry/packages/yarnpkg-core/sources/scriptUtils.ts

Line 697 in 57081c0

return miscUtils.mapAndFilter.skip;

).

Also added a unit test to guard this behavior.

No PR for yarn v6. This problem doesn't exist in yarn v6, it has solved the problem structurally https://github.com/yarnpkg/zpm/blob/def394488933b0c5037e70d82a2f4842089497e4/packages/zpm/src/project.rs#L1352
...

Verification

I'm testing it using the example in #7264 , that we start a devserver and the error is on the unrelated eslint.

command	PnP — before	PnP — after	node-modules (unaffected)
yarn run start	Couldn't find eslint@npm:8.57.1 in the currently installed PnP map	✓ boots Next.js	✓ boots Next.js
yarn next --version	same as above	✓ Next.js v14.2.15	✓ Next.js v14.2.15
yarn bin next	same as above	✓ prints the next bin path	✓ prints the path
yarn bin (list)	same as above	✓ lists next	✓ lists next
yarn node -e "require.resolve('next')"	same as above	✓ resolves	✓ resolves
yarn eslint --version	same as above	Couldn't find a script named "eslint"	same as left
yarn node -e "require.resolve('eslint')"	same as above	…tried to access eslint, but it isn't declared…	same as left

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.