Sync migrations

[carletex]

Since we merged #24 schema.prisma was out of sync with the migrations files, so runningprisma migrate dev was creating a new migration file (removing the the index & the default value) + failing to apply.

What I did:

• Start with an empty database
• prisma migrate deploy (to import the existing migration file, without checking the schema)
• prisma db pull to introspect the database (it auto-updated the schema.prisma file)

With this, everything runs smoothly now! I also updated the README with the new migrate instructions.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
collectivedaoarchives-catalog	✅ Ready (Inspect)	Visit Preview	Sep 14, 2023 2:29pm

[carletex]

Also removed shadowDatabaseUrl = env("POSTGRES_URL_NON_POOLING") from schema.prisma which is not needed anymore, and it was causing an error:

1 migration found in prisma/migrations

Error: P3005

The database schema is not empty. Read more about how to baseline an existing production database: https://pris.ly/d/migrate-baseline

(see prisma/prisma#19234)