Investigate Yarn 2 Plug'n'Play

**What would you like to be added**:
Verify support for Yarn's Plug'n'Play package resolution.

**Why is this needed**:
This is potentially incompatible with the current `yarn.lock`-based scanning of a directory and `node_modules` handling.

**Additional context**:
Yarn 1 by default duplicates npm's behavior of putting things in the `node_modules` directory. [Yarn 2 by default](https://yarnpkg.com/getting-started/migration#why-should-you-migrate) uses [Plug'n'Play](https://yarnpkg.com/features/pnp), which does not put files directly in `node_modules` but uses another strategy.

Start by reviewing the current yarn.lock-based directory scanning and node_modules handling, then compare them with Yarn 2 Plug'n'Play's package-resolution approach. Done means determining whether Plug'n'Play is supported and documenting or implementing the compatibility work required.

Written by the indexing model from the issue text.