feat(docker): pre-extract the driver in images to avoid /tmp unpacking

[yury-s]

Summary

• The official images now extract the driver once at build time and reuse it at runtime, so the library no longer unpacks the Node.js binary and playwright-core package into /tmp on every Playwright.create() — addressing the immutable-infra concern in [Feature] Java library poor playwright/java docker image integration #1268.
• New CLI install-driver [dir] command extracts the driver (the playwright-core package + the host Node.js binary) into a fixed directory.
• New PLAYWRIGHT_DRIVER_DIR environment variable (env equivalent of the playwright.cli.dir system property) points Playwright at a preinstalled driver directory via PreinstalledDriver — zero extraction.
• Dockerfiles (jammy/noble/resolute) run install-driver at build into /ms-playwright-driver and bake PLAYWRIGHT_DRIVER_DIR for runtime.

Notes

• The bundled, version-matched host Node.js is the single node that gets pre-extracted, so no separate Node.js install is needed.
• Verified: install-driver produces a self-contained package/cli.js + node; with PLAYWRIGHT_DRIVER_DIR set, driverDir is that path (no /tmp) and Chromium launches. TestInstall covers the extract-and-reuse flow.
• Did not run an actual docker build here; the Java side is verified end-to-end and the Dockerfile edits mirror the existing install steps.

Fixes #1268