chore: refactor serialization to be driven by expected types from Postgres

[samwillis]

This is based on #306 but additionally refactors much of the type handling. It also lays the foundation for users to add they own serialises and parser to a PGlite instance either directly or via a plugin/extension - this will come in a later PR.

In the old version type serialization was driven by inferring the type on the JS side, converting to a serialised string, and then setting the type OID on the query for each parameter.

This new version uses the "describe" protocol message to get the expected type of each parameter in a query, and then try and serialise the value based on that. This is based on how it's done in postgres.js

[github-actions[bot]]

Built bundles:

• Postgres WASM: https://github.com/electric-sql/pglite/actions/runs/11019746981/artifacts/1973217327
• Interim build files: https://github.com/electric-sql/pglite/actions/runs/11019746981/artifacts/1973217487
• PGlite: https://github.com/electric-sql/pglite/actions/runs/11019746981/artifacts/1973243260
• Demos: https://github.com/electric-sql/pglite/actions/runs/11019746981/artifacts/1973257044

[github-actions[bot]]

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

[samwillis]

Hey @alexgleason, could you take a look at this and see if it works with your app?

[alexgleason]

@samwillis My tests are passing with this branch. Thank you!! :+1: