Describe the bug
Attempting to use latest v5.1.1, clean application. For reference I've been attempting to update an application from v5.0.2 to latest and was experiencing issues with Prisma, related to turbopack builds that were enabled recently. To debug further, I attempted to try a clean installation from the template and experienced the same issue (Neon Postgres)
I have applied the pull request from https://github.com/vercel/next-forge/pull/644/files as I also ran into this issue initially.

Error [PrismaClientInitializationError]:
Invalid prisma.page.findMany() invocation:

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.

This is likely caused by tooling that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" to the deployment folder.
Ensure that you ran prisma generate and that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied to "generated/client".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-tooling-investigation

The following locations have been searched:
/var/task/apps/app/generated/client
/ROOT/packages/database/generated/client
/vercel/path0/packages/database/generated/client
/ROOT/packages/database/.prisma/client
/tmp/prisma-engines
at hE.handleRequestError (.next/server/chunks/ssr/[root-of-the-server]__50a49d6e..js:115:8157)
at hE.handleAndLogRequestError (.next/server/chunks/ssr/[root-of-the-server]__50a49d6e..js:115:6918)
at hE.request (.next/server/chunks/ssr/[root-of-the-server]__50a49d6e..js:115:6625)
at async e (.next/server/chunks/ssr/[root-of-the-server]__50a49d6e..js:127:7513)
at async m (.next/server/chunks/ssr/[root-of-the-server]__e401dd23._.js:1:8945) {
clientVersion: '6.16.3',
errorCode: undefined,
retryable: undefined,
digest: '1245725288'
}

next-forge version
I am using version v5.1.1

To Reproduce
Steps to reproduce the behavior:

1. Clone repository and use Vercel to make a new deployment - with required env variables
2. Open up app application - Oops, something went wrong
3. See logs from app

Expected behavior
Builds correctly