chore: Bump Yarn to 4.16.0 (#4019)

This bumps Yarn to `4.16.0`.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Small plugin-only change to dependency loading; no auth, data, or
product logic touched.
> 
> **Overview**
> Updates the local **`plugin-workspaces-filter`** plugin so it stays
compatible with **Yarn 4.16.0** after the bump.
> 
> In both **`FilterListCommand`** and **`FilterRunCommand`**,
**`minimatch`** is no longer loaded with dynamic
**`import('minimatch')`**. It now uses Node’s
**`createRequire(__filename)`** so the dependency resolves from the repo
(e.g. root **`devDependencies`**) instead of Yarn’s restricted plugin
**`require`** sandbox.
> 
> No runtime behavior change for **`--include` / `--exclude`** glob
filtering—only how **`minimatch`** is resolved at command execution
time.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
cb3187c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: Mrtenz

.yarn/plugins/local/plugin-workspaces-filter.js

@@ -71,10 +71,13 @@ module.exports = {
       }
 
       async execute() {
-        // Note: We have to import `minimatch` here, because Yarn will always
+        // Note: We have to require `minimatch` here, because Yarn will always
         // load the plugin, even if the command is not used, and `minimatch`
-        // may not be installed.
-        const { minimatch } = await import('minimatch');
+        // may not be installed. We use `createRequire` from Node's built-in
+        // `module` package to bypass Yarn's restricted plugin `require`, which
+        // only allows access to Yarn's own bundled packages.
+        const { createRequire } = require('module');
+        const { minimatch } = createRequire(__filename)('minimatch');
 
         const configuration = await Configuration.find(
           this.context.cwd,
@@ -203,10 +206,13 @@ module.exports = {
       }
 
       async execute() {
-        // Note: We have to import `minimatch` here, because Yarn will always
+        // Note: We have to require `minimatch` here, because Yarn will always
         // load the plugin, even if the command is not used, and `minimatch`
-        // may not be installed.
-        const { minimatch } = await import('minimatch');
+        // may not be installed. We use `createRequire` from Node's built-in
+        // `module` package to bypass Yarn's restricted plugin `require`, which
+        // only allows access to Yarn's own bundled packages.
+        const { createRequire } = require('module');
+        const { minimatch } = createRequire(__filename)('minimatch');
 
         const configuration = await Configuration.find(
           this.context.cwd,