Update Rush.js to latest and PNPM to 11.x

[GytisCepk]

While running rush audit, I get the following:

 ERR_PNPM_AUDIT_BAD_RESPONSE  The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits/quick) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead. See the following docs for more info: https://api-docs.npmjs.com/#tag/Audit"}. Fallback endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead. See the following docs for more info: https://api-docs.npmjs.com/#tag/Audit"}

This has been fixed in pnpm 11, so we might as well update to it.

[GytisCepk]

Rush.js does not currently support PNPM 11 (at least not properly). This causes issues with our configs like globalOverrides not getting copied over to a place where pnpm would actually read it.

I see 2 options currently:

• Proceed with pnpm 11 upgrade and hack around issues using .pnpmfile.cjs
  • While this may work, I'm not a fan, as this would require add significant complexity to our Rush setup without a clear pay off
• Use PNPM 11 only for rush audit and wait for Rush.js to fix their PNPM 11 issues
  • In my opinion, this is the best solution given circumstances
  • This may confuse @hl662's agent a bit as process for ignoring GHSA changes
  • Use PNPM 11 for rush audit #9506

[GytisCepk]

Putting this on hold until PNPM 11 works on Rush.js