Using Prisma file alongside Wasp

[infomiho]

This is some highly experimental work to move entities outside of the Wasp file and to put them in a regular schema.prisma file.

In this PR we:

• extend the model parser to parse lists of Prisma models
• extend the PSL parser to include enums
• parse the Prisma file and:
  • store the Prisma schema in AppSpec
  • inject the entities from Prisma file to the Wasp AST
• extend the LS to watch and parse the Prisma file as well
• we use DB extensions from the Prisma file directly
• we use the DB provider from the Prisma file directly

Closes #2002
Closes #2137

Left to do

• Validate the Wasp AST to ensure users don't define entities in the Wasp file? We are not sure if we want to do this
• Make sure that validating schema.prisma in node_modules doesn't throw an error openBinaryFile: does not exist (No such file or directory
• Make sure to regenerate the schema.prisma file if it changes in the node_modules/ (i.e. user runs npx prisma command and alters the Prisma schema)
• Make Wasp AI use the new structure (prompts, Prisma file handling) Updates Wasp AI to work with the Prisma file #2080
• E2e tests Update e2e tests to work with Prisma file #2095
• Basic template
• Validate that user set env("DATABASE_URL") for DB url

Probably in a separate PR

• Update the docs
  • Data model docs
  • Tutorial
  • Any other part that mentions entities
• Write new migration docs
• Starter templates
  • Embeddings template
  • Open SaaS template
  • Todo Typescript template
• Example apps
  • waspc/examples apps
  • examples/ apps
  • headless tests app

[Martinsos]

Awesome stuff @infomiho ! Anything specific you want looked at at the moment, or is all good for now?

[Martinsos]

@infomiho left some more comments, I think this should be the last round! We are super close now, awesome!

[Martinsos]

Wohooo that is it, nice! I didn't do a final sweep through all the code, if you want to do that you can, maybe it is not needed though. Anyway, great job! You can merge.