chore:grouping prisma models into separate domain files

[timDeHof]

Description

The prisma dependencies was updated to the latest version to use the new feature of multiple schemas. Also the main schema file was refactored to have related models grouped into a same domain files with clear naming conventions.

Issue link

Fixes # (issue)
https://app.clickup.com/t/86b0zg2qf

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature updates / changes
• Tests
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

1. run yarn
2. run yarn seed to check if the prisma will still populate the database
3. run yarn test:docker to check if test still pass

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have updated the change log

Useful links:

how-to-use-existing-prisma-cli-commands-with-multiple-prisma-schema-files

[timDeHof]

I noticed that the tests have passed. But if you try to push, studio, or migrate the db, you will face with errors like this:

I don't know if it's only an issue in docker or if its occurring on local computers too. it seems that others are issues with this feature too.
prisma/prisma#24413

UPDATE:I ran yarn in docker to update the packages and now yarn studio:test:docker worked.

[cherylli]

ran all the more frequently used prisma commands and tests, all good 👍

[JoshuaHinman]

Everything passed without any hiccups - seed, migrate, studio all worked - looks good!