chore(deps): bump @prisma/client from 4.14.0 to 4.16.2 in /orm

[dependabot]

Bumps @prisma/client from 4.14.0 to 4.16.2.

Release notes

Sourced from @​prisma/client's releases.

4.16.2

Today, we are issuing the 4.16.2 patch release.

Fixes in Prisma Client

• 4.16: (MongoDB) Generated types for list composites are incorrect
• Getting wrong types with prisma client extensions
• Prisma Client fluent API does not work with extends anymore on 4.16.1
• Prisma Client Extensions: $allModels: { $allOperations } sets query type to never
• Result types are incorrectly inferred when undefined explicitly passed to select/include

4.16.1

Today, we are issuing the 4.16.1 patch release.

Fixes in Prisma Client

• Field references are not available on extended clients
• 4.16.x cannot wrap $extend in factory function when compilerOptions.composite is true
• Prisma Schema Type inside a Type not generating a right Payload
• Query in findMany in prisma extends returns a wrong type
• 4.16.0 Count query is not returning the right type when in a transaction
• FindMany returns wrong type after extending prisma client
• Can't specify $queryRawUnsafe return type after extending prisma client

4.16.0

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

Highlights

This release promotes the following Preview features to General Availability:

• Prisma Client extensions
• Ordering by nulls first and last
• Count by filtered relation

Prisma Client extensions are Generally Available

Today, we’re very excited to announce that Prisma Client extensions are Generally Available and production-ready! This means you can use the feature without the clientExtensions Preview feature flag.🚀

Prisma Client extensions are a powerful new feature for adding functionality on top of your Prisma Client in a type-safe manner. With this feature, you can create simple, but flexible solutions.

Prisma Client extensions have 4 different types of components that can be included in an extension:

• Result extensions components: add custom fields and methods to query result objects, for example, virtual/computed fields.
• Model extensions components: enable you to add new methods to your models alongside existing model methods such as findMany.
• Query extensions components: let you hook into the lifecycle of a query and perform side effects, modify query arguments, or modify the results in a type-safe way. These are an alternative to middleware that provide complete type safety and can be applied in an ad-hoc manner to different extensions.
• Client extensions components: allow you to add new top-level methods to Prisma Client. You can use this to extend Prisma Client with functionality that isn’t tied to specific models.

</tr></table> 

... (truncated)

Commits

• 8089b6c fix: Correctly infer types when select/include are undefined (#20018)
• 4f33ffe fix(client): extensions with fluent api (#19942)
• fda93b9 chore(deps): patch 4.16.x 4.16.1-1.4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (...
• 4f3439a fix(client): Optional composites (#19920)
• 0ac2a12 fix(client): extensions backwards compatibility (#19896)
• 199b9e7 fix(client): field references via extensions (#19893)
• 9b7b43e fix(client): extensions having wrong return types (#19875)
• 7ddf99d fix(client): Default selection for composite lists (#19887)
• c6982eb fix(client): Ensure tsc can create a declaration out of extended client (#19885)
• cd08a44 fix(client): extensions raw query manual typing (#19877)
• 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 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)

[codecov]

Codecov Report

Merging #566 (e9f1d79) into develop (b2f5f34) will not change coverage.
The diff coverage is n/a.

❗ Current head e9f1d79 differs from pull request most recent head 00ab80c. Consider uploading reports for the commit 00ab80c to get more accurate results

@@           Coverage Diff            @@
##           develop     #566   +/-   ##
========================================
  Coverage    93.99%   93.99%           
========================================
  Files           37       37           
  Lines         1082     1082           
  Branches       230      230           
========================================
  Hits          1017     1017           
  Misses          58       58           
  Partials         7        7           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.