Own Playground SQLite package alias compatibility in Codebox runtime packaging

[chubes4]

Problem

wp-gym currently carries an install-time workaround that copies Playground's sqlite-database-integration.zip to sqlite-database-integration-trunk.zip under node_modules/@wp-playground/wordpress-builds. That is runtime/package compatibility glue, not wp-gym eval semantics.

If the Codebox runtime needs this alias for clean installs, Codebox should own the compatibility handling or remove the need for it by depending on a Playground package/build that has the expected filename.

Desired outcome

Make Codebox installs self-contained for consumers so downstream packages do not need to mutate @wp-playground/wordpress-builds during install.

Acceptance criteria

• A clean Codebox consumer install can boot the WordPress Playground runtime without downstream SQLite alias scripts.
• Any required aliasing/normalization is implemented in Codebox packaging/runtime setup or removed by dependency alignment.
• The behavior is covered by a clean-install or package smoke test.
• wp-gym can remove scripts/ensure-playground-sqlite-alias.mjs and direct Playground runtime dependencies after this lands.

Downstream evidence

Current workaround lives in wp-gym/scripts/ensure-playground-sqlite-alias.mjs and direct dependencies in wp-gym/package.json.