Upgrade Yarn

[lensbart]

Copied from here. I didn’t create an issue because this is not a bug, strictly speaking.

I think it would be a good idea to upgrade the repository version of Yarn so that it imposes stricter rules on dependencies. There have been several issues with Yarn that would have been caught by using Yarn 2 or higher:

• [Bug]: Yarn 3 support? #683
• feat: Yarn PnP support in monorepo #1111
• [Bug]: incorrectly configured peer dependencies (remix-run/node, remix-run/express) #1707
• remix-eslint-config throws an error when using Yarn PnP #3715
• unable to build and run in yarn workspaces pnp monorepo #4106
• Uncaught Error: Dynamic require of "fs/promises" is not supported - when importing json from @remix-run/node #4236
• Doesn’t work with Yarn PnP #4346
• eslint-plugin-import should be a peer dependency of @remix-run/eslint-config #4448
• Unable to "npm run build" remix app after upgrading to 1.8.0 #4764
• Cannot find module error on fresh build #5180
• Remix 1.16 breaks yarn pnp #6288
• Yet another Yarn 3 PNP issue #6640
• @remix-run/web-fetch tries to access @remix-run/web-blob, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound. #7434
• … (non-exhaustive)

Perhaps it would also be a good idea to switch to the Yarn PNP module resolution mechanism.

[lensbart]

After upgrading, npx yarn-deduplicate could be replaced by the built-in yarn dedupe. Also, yarn dlx is the idiomatic way to run scripts without installing them first, instead of npx.