Use prisma-test-utils to test Database->Introspection->Prisma Client flow

[janpio]

We want to use prisma-test-utils to give us confidence for our standard flow where you start with a database, introspect it to get a Prisma Schema, generate a Prisma Client and then use it to read and write data with your app. Right now, the combination of an unlimited number of schemas that could be out there, and the Prisma Client we generate in the end, could have problems and not work.

The "Seed" functionality of prisma-test-utils might be able to cover the "write data" part. If during writing something breaks (Can not be inserted because database schema does not match), or after reading back the data, it changed to something else (shortened string, empty string, etc), we know we have a bug somewhere that needs to be fixed.

The end goal is to put this into CI to fully automate the flow and verification of the results. (We already have a private project that tests https://github.com/prisma/database-schema-examples/ and many more schemas for introspect and generate - the end result is just not tested properly yet).