Relates to

Issue: #1809

Risks

Low risk, if any would only impact dev env (since no one is running with an sqlite/pglite adapter in prod right?).

Background

What does this PR do?

Add a new db adapter for PGLite.

What kind of change is this?

Features

Why are we doing this? Any context or related work?

Faster dev env

Documentation changes needed?

My changes require a change to the project documentation, and I have updated the documentation accordingly.
For now I only specified added the new db adapter in the adapters section of the doc, and not replaced all the dev recommendation from SQLiteAdapter to PGLite.

Testing

Where should a reviewer start?

Check the diff between the adapter-pglite and the adapter-postgres.
A few changes made but not super significative:

• Exploit pglite.transaction(...) instead of manual pg tx
• Typed db.query call
• Remove stuff related to distant connection (the withRetry), the circuitBreaker usage could also be removed, but I keeped it to reduce the amount of changes.

Detailed testing steps

Multiple options:

• In the packages/core/env.test, set TEST_DATABASE_CLIENT=pglite
• By manually testing, you can add a PGLITE_DATA_DIR=../pgLite/ # or "memory://" for in mem pglite env variable and ensure everything is running smoothly
• Or manually running everything const db = new PGLiteAdapter(options)

Discord username

konfeature