Begin moving to postgres spilo + adding pgvector (#8309)

We will remove the `twenty-postgres` image that was used for local
development and only use `twenty-postgres-pilo` (which we use in prod),
bringing the development environment closer to prod and avoiding having
to maintain 2 images.


Instead of provisioning the super user after the db initialization, we
directly rely on the superuser provided by Spilo for simplicity. We also
introduce a change that tries to create the right database (`default` or
`test`) based on the context.
  

How to test:
```
docker build -t twentycrm/twenty-postgres-spilo:latest -f ./packages/twenty-docker/twenty-postgres-spilo/Dockerfile .
docker images --no-trunc | grep twenty-postgres-spilo
postgres-on-docker:
	docker run \
	--name twenty_pg \
	-e PGUSER_SUPERUSER=twenty \
	-e PGPASSWORD_SUPERUSER=twenty \
	-e ALLOW_NOSSL=true \
	-v twenty_db_data:/home/postgres/pgdata \
	-p 5432:5432 \
	REPLACE_WITH_IMAGE_ID
```

packages/twenty-server/scripts/truncate-db.ts

@@ -21,6 +21,14 @@ async function dropSchemasSequentially() {
     // Iterate over each schema and drop it
     // This is to avoid dropping all schemas at once, which would cause an out of shared memory error
     for (const schema of schemas) {
+      if (
+        schema.schema_name === 'metric_helpers' ||
+        schema.schema_name === 'user_management' ||
+        schema.schema_name === 'public'
+      ) {
+        continue;
+      }
+
       await performQuery(
         `
         DROP SCHEMA IF EXISTS "${schema.schema_name}" CASCADE;