Update jest setup for Prisma's multiSchema

[zaiyou12]

issue #10009

Description

In multi-schema Prisma projects, the teardown process in Jest setup files does not dynamically handle schema prefixes, leading to issues when trying to clean up test data. This is relevant for projects that using Prisma's preview feature multiSchema.

Problem

The original teardown logic in the Jest setup file does not account for models located in different schemas, resulting in errors during the test cleanup phase. Specifically, the error occurs when attempting to delete data from tables without specifying the correct schema prefix, leading to failed tests due to unresolved table references.

Changelogs

To address this issue, I've made quick fix to the jest.setup.js configuration to dynamically extract schema information from the Prisma schema file and apply this information during the teardown process. This ensures that raw SQL commands are executed against the correct schema, allowing for proper cleanup of test data across multiple schemas.

• Extract Model Schemas: Since Prisma getDMMF doesn't return schema with table name, I need to implement a function extractModelSchemas to parse the Prisma schema file and extract model-to-schema mappings. This function uses regular expressions to find model definitions and their schema annotations.
• Update Teardown Logic: Modified the teardown function to utilize the extracted schema information, prefixing SQL commands with the correct schema name.

[ahaywood]

@zaiyou12 thanks for taking the time to submit this PR, excited to take a look at your code...