build(deps): bump @prisma/client from 5.15.0 to 5.16.1

[dependabot]

Bumps @prisma/client from 5.15.0 to 5.16.1.

Release notes

Sourced from @​prisma/client's releases.

5.16.1

Today, we are issuing the 5.16.1 patch release to fix an issue in Prisma client.

Fix in Prisma Client

• dotenv loading issue with PrismaClient
• Prisma Seed Script Fails After Upgrading to v5.16.0 (DATABASE_URL Error)

5.16.0

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Omit model fields globally

With Prisma ORM 5.16.0 we’re more than happy to announce that we’re expanding the omitApi Preview feature to also include the ability to omit fields globally.

When the Preview feature is enabled, you’re able to define fields to omit when instantiating Prisma Client.

const prisma = new PrismaClient({
  omit: {
    user: {
      // make sure that password is never queried.
      password: true,
    },
  },
});

You’re also able to omit fields from multiple models and multiple fields from the same model

const prisma = new PrismaClient({
  omit: {
    user: { 
      // make sure that password and internalId are never queried.
      password: true,
      internalId: true,
    },
    post: {
      secretkey: true,
    },
  },
});

With both local and global omit, you now have the flexibility to completely remove sensitive fields while also tailoring individual queries. If you need the ability to generally omit a field except in a specific query, you can also overwrite a global omit locally

</tr></table> 

... (truncated)

Commits

• c26bbfe fix(client): restore loading .env files in @prisma/client (#24649)
• 1d34b5b chore(deps): update engines to 5.16.0-24.34ace0eb2704183d2c05b60b52fba5c43c13...
• d433bb7 feat(client): provide a workaround for Vitest's struggles with "getQueryEngin...
• 65e17a0 chore(deps): update engines to 5.16.0-23.d56fe2ee624826f693e591a3035694073d17...
• c64e77f chore(deps): update engines to 5.16.0-21.9f3337c21c619aa48465f3766f6466c74ec7...
• 6a6646c fix(cli): Always resolve output relatively to a file it defined in (#24598)
• 617042d chore(deps): update engines to 5.16.0-20.bd07760d57443d11e2a958fd18bf524bbac1...
• a1121f1 chore(deps): update dependency @​swc/core to v1.6.3 (#24546)
• dbad2af chore(deps): update dependency wrangler to v3.61.0 (#24578)
• 8808e17 feat(client): Implement global omit configuration (#24513)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)