Port PGlite initialization and query-result contracts

Context

The sequential Bun corpus frontier is js/third_party/@electric-sql/pglite/pglite.test.ts at position 3950/4708, following completed DuckDB Node API work in #209. This contributes to #66.

Current gap

The single-test TypeScript module is classified as unsupported module syntax because the scoped @electric-sql/pglite import is not yet represented in Home's module compatibility layer.

Acceptance criteria

• Scoped @electric-sql/pglite import prepares and resolves.
• new PGlite() initializes with the tested lifecycle.
• query('SELECT version()') returns the expected rows, field metadata, and affected-row count.
• The existing Linux/CI TODO guard remains meaningful.
• Pin the exact passing result in the permanent third-party gate.

Completed on main in 70642e838cb5d8b0c66aa3e6b4a16c51ffb01c22 (feat(third-party): port PGlite query contracts).

js/third_party/@electric-sql/pglite/pglite.test.ts is green at 1 passed, 0 failed, 0 TODO, 0 unsupported. Scoped import resolution, PGlite initialization, exact PostgreSQL 17.5 WASM version row/field metadata, affected-row count, and closed-database behavior are represented. The exact result is pinned in the permanent third-party gate, which passes in full.

The sequential frontier advances through 3950/4708. Fastify WebSocket integration is tracked next in #211.