Bump @wp-playground/* and @php-wasm/* to 3.1.26 (#3325)

## Related issues

- Related to none — routine dependency bump

## How AI was used in this PR

Claude Code performed the version bump across all package.json files,
reviewed the
[v3.1.23](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.23),
[v3.1.24](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.24),
[v3.1.25](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.25),
and
[v3.1.26](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.26)
release notes for breaking changes, ran `npm install` to refresh
`package-lock.json`, and verified `npm run typecheck` and `npm test`
both pass.

## Proposed Changes

- Bump `@wp-playground/*` and `@php-wasm/*` packages from `3.1.22` →
`3.1.26` (latest) in all five `package.json` files (`apps/cli`,
`apps/studio`, `apps/ui`, `tools/benchmark-site-editor`,
`tools/common`).
- Refresh `package-lock.json` accordingly.
- Versions remain exact-pinned per the project's bundling rules.

### Release notes review (3.1.23 → 3.1.26)

No breaking changes across the four releases:

-
**[3.1.23](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.23)**
— Restored bundled type declarations for `@wp-playground/client` (Studio
doesn't consume this package).
-
**[3.1.24](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.24)**
— No changelog entries.
-
**[3.1.25](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.25)**
— Sets `curl.cainfo` alongside `openssl.cafile`; exports Zend symbols
for compiling extensions; limits external extensions to JSPI; introduces
`@php-wasm/compile-extension` workflow; skips `prefetchUpdateChecks()`
when WordPress is disabled. All additive.
-
**[3.1.26](https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.26)**
— `extraFiles` support for custom PHP extensions; new
`PHPExtensionManifest` shape (only consumed by the new
`compile-extension` tool, which Studio does not use); website-only PHP
snippet UX changes.

## Testing Instructions

- Pull the branch and run `npm install`.
- Run `npm run typecheck` — should pass across all workspaces.
- Run `npm test` — should pass (160 test files, 1506 tests on local
run).
- Run `npm start`, create a new local site, and verify it boots and
serves WordPress correctly.
- Optional: build the CLI (`npm run cli:build`) and exercise `studio
site` / `studio preview` commands.

## Pre-merge Checklist

- [x] Have you checked for TypeScript, React or other console errors?

Author: wojtekn

apps/cli/package.json

@@ -31,16 +31,16 @@
 		"@mariozechner/pi-coding-agent": "0.70.2",
 		"@mariozechner/pi-tui": "0.70.2",
 		"@modelcontextprotocol/sdk": "^1.27.1",
-		"@php-wasm/node": "3.1.22",
-		"@php-wasm/universal": "3.1.22",
-		"@php-wasm/util": "3.1.22",
+		"@php-wasm/node": "3.1.26",
+		"@php-wasm/universal": "3.1.26",
+		"@php-wasm/util": "3.1.26",
 		"@vscode/sudo-prompt": "^9.3.2",
 		"@wordpress/i18n": "^6.14.0",
-		"@wp-playground/blueprints": "3.1.22",
-		"@wp-playground/cli": "3.1.22",
-		"@wp-playground/common": "3.1.22",
-		"@wp-playground/storage": "3.1.22",
-		"@wp-playground/wordpress": "3.1.22",
+		"@wp-playground/blueprints": "3.1.26",
+		"@wp-playground/cli": "3.1.26",
+		"@wp-playground/common": "3.1.26",
+		"@wp-playground/storage": "3.1.26",
+		"@wp-playground/wordpress": "3.1.26",
 		"archiver": "^7.0.1",
 		"atomically": "^2.1.1",
 		"cli-table3": "^0.6.5",

apps/studio/package.json

@@ -97,7 +97,7 @@
 		"@types/winreg": "^1.2.36",
 		"@types/yauzl": "^2.10.3",
 		"@vitejs/plugin-react": "^5.1.4",
-		"@wp-playground/blueprints": "3.1.22",
+		"@wp-playground/blueprints": "3.1.26",
 		"electron": "^41.4.0",
 		"electron-devtools-installer": "^4.0.0",
 		"electron-vite": "^5.0.0",

apps/ui/package.json

@@ -24,7 +24,7 @@
 		"@wordpress/react-i18n": "^4.44.0",
 		"@wordpress/theme": "0.11.0",
 		"@wordpress/ui": "0.11.0",
-		"@wp-playground/blueprints": "3.1.22",
+		"@wp-playground/blueprints": "3.1.26",
 		"clsx": "^2.1.1",
 		"react": "^18.2.0",
 		"react-dom": "^18.2.0",