Tooling modernization

[vecerek]

Is your feature request related to a problem? Please describe.

I'm currently struggling to add a new codegen plugin in #701. The issue is caused by an inexplicable yarn dependency resolution issue that happens only when I add this new package. The current version of yarn in this project is pretty old (1.22.22). I think I would have a much easier time troubleshooting the issue if the codebase used the latest version of Yarn. The issue would probably not exist at all, if the codebase were to use Yarn PnP which ensures correct dependency hoisting across all workspaces. But to get there, there's a lot to be fixed. I noticed that many of the current packages do not declare all of their dev dependencies in their package.json file. Also, when I run yarn install, I see tons of warnings about unmet peer dependencies. The side effect of migrating to PnP would be that all these issues would also get fixed.

Describe the solution you'd like

I would like to explore the possibility of incremental migration towards the latest version of Yarn and eventually PnP. I already opened a few PRs as a PoC:

• chore: add packageManager to the manifest #732
• chore: upgrade yarn #733
• chore: address issues reported by yarn doctor #734

Describe alternatives you've considered

Additional context