fix: Vite inline prisma values

[jacobparis]

Using the Vite dev server, client side navigations are inexplicably failing when trying to navigate to a page which imports (either directly or indirectly) any schema values from @trigger.dev/database and uses them for actual code. Importing and using them as types seems to be ok, and importing the prisma package also works.

I've tested using prisma-zod-types and importing those results instead, with the same issue.

On occasion I can get it to show an error message, which looks like @trigger.dev/database does not provide an export TaskRunStatus as if the prisma client hadn't been generated. However VS Code can resolve the types fine, and it works on SSR as well. I'm not sure if this error is at the pnpm layer or with Vite directly, or possibly part of the way it optimizes dependencies doesn't work with prisma's codegen over pnpm's symlinks. Lots of moving parts here.

This PR unblocks the process by finding every place in the webapp where the prisma client is used at runtime and inlining the values. There's a fair bit of duplication here because I kept each one to its own file. We could find a real home for these but I'd consider this a temporary solution at the moment until Vite gets sorted out.

Closes #

✅ Checklist

• I have followed every step in the contributing guide
• The PR title follows the convention.
• I ran and tested the code works

---

Testing

[Describe the steps you took to test this change]

---

Changelog

[Short description of what has changed]

---

Screenshots

[Screenshots]

💯

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0a7ad23

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR