feature: wasmModule and fsBundle options and caching of module+fsBundle

[samwillis]

This adds additional options for the wasmModule and fsBundle, along with caching of the default ones if used.

This should enable a route to running in a Cloudflare worker (pending further changes) as you can do something like:

import { PGlite } from '@electric-sql/pglite';
import wasm from '@electric-sql/pglite/dist/postgres.wasm';
import fsBundle from '@electric-sql/pglite/dist/postgres.wasm';

pg = await PGlite.create({
    wasmModule: wasm,
    fsBundle: fsBinary,
});

We had something working similar to this in the old v0.1.n version of PGlite on Cloudflare

Fixes: #329 #81

[github-actions[bot]]

Built bundles:

• Postgres WASM: https://github.com/electric-sql/pglite/actions/runs/11019830343/artifacts/1973242070
• Interim build files: https://github.com/electric-sql/pglite/actions/runs/11019830343/artifacts/1973242197
• PGlite: https://github.com/electric-sql/pglite/actions/runs/11019830343/artifacts/1973269086
• Demos: https://github.com/electric-sql/pglite/actions/runs/11019830343/artifacts/1973283244

[github-actions[bot]]

🚀 Deployed on https://66f30841814dd9060fe0066b--pglite.netlify.app