playwright + pnpm gyp images: tag build for node 22.22.0 + pnpm 11.5.2 + playwright 1.59.1 (Planner consumer pin)

[jclaveau]

Planner just bumped pnpm 10.30.3 → 11.5.2 and the prebuilt tag we pin against (ubuntu-dood-playwright-gyp-sudoer:ubuntu24.04-node22.22-pnpm10.30-pw1.59-gyp-sudoer) now lies about pnpm, so corepack inside the container has to re-fetch on every job.

Versions Planner runs against today:

• Node 22.22.0 (.nvmrc)
• pnpm 11.5.2 (packageManager field)
• Playwright 1.59.1 (catalog)

Asking for one build of two flavors with the same tuple so I can stop drifting against pnpm10.30:

• ubuntu-dood-playwright-gyp-sudoer:ubuntu24.04-node22.22-pnpm11.5-pw1.59-gyp-sudoer (used by tests-e2e-front.yml:38, mandatory)
• ubuntu-dood-pnpm-gyp:ubuntu24.04-node22.22-pnpm11.5-pw1.59-gyp (used by tests-e2e-back.yml:34, currently on :latest — nice-to-have, lets me pin too)

Not asking for the full versioned namespace from #37 — just this one tuple so Planner can pin both consumers.

Open questions:

• Build the .0 tuple now, or hold for chore(deps): update node.js to v22.22.3 #64 (node 22.22.3) + chore(deps): update playwright to v1.60.0 #65 (pw 1.60.0) so the tag covers a more durable point?
• pnpm11.5 vs pnpm11.5.2 in the tag — repo convention currently truncates at minor; keep that, or full patch?

Out-of-scope: full matrix (#37), webkit branches (#61), musl FF (#60), playwright-dind:latest consumer in build-quasar.yml (not on this tuple).