chore(deps): bump @prisma/generator-helper from 3.12.0 to 4.10.1 in /packages/cpg-template-typescript/template

[dependabot]

Bumps @prisma/generator-helper from 3.12.0 to 4.10.1.

Release notes

Sourced from @​prisma/generator-helper's releases.

4.10.1

Today, we are issuing the 4.10.1 patch release.

Fixes in Prisma Client

• Prisma Client falsely validates directUrl env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)
• 4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.

4.10.0

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

Highlights

Improved CLI support for connection poolers

When working with connection poolers such as the Prisma Data Proxy, Accelerate or pgBouncer, it is necessary to use a different URL to connect to the database when using Prisma Client and Prisma Migrate.

We're introducing a new datasource property directUrl to improve this. When the directUrl property is present, the Prisma CLI will use it to connect to the database for tasks such as introspection and migrations.

# .env
# Connection to Prisma Data Proxy. Used by Prisma Client.
DATABASE_URL="prisma://__HOST__/?api_key=__KEY__"
# Connection to the database. Used for migrations and introspection.
DIRECT_URL="postgresql://__USER__:__PASSWORD__@__HOST__:__PORT__/__DATABASE__"

// ./prisma/schema.prisma
generator client {
  provider = "prisma-client-js"
}
datasource db {
provider  = "postgresql"
url       = env("DATABASE_URL")
directUrl = env("DIRECT_URL")
}

To learn more, refer to our documentation.

Introspection support for PostgreSQL views

We introduced initial support for database views in 4.9.0 with the addition of the view keyword. This release introduces introspection support for PostgreSQL views. You can run prisma db pull against your database to populate your Prisma schema with your views.

To learn more, refer to our documentation on views introspection. Try it out and let us know your thoughts in this GitHub issue.

Improved introspection for unsupported database functionality & partitioned tables

... (truncated)

Commits

• a3e9bae chore(deps): update jest (#17130)
• a256dbb chore(deps): update devdependencies (non-major) (#16290)
• cc519a8 feat: stop downloading introspection-engine (#17301)
• f6e1ca6 feat: remove prisma-fmt binary (#16923)
• b51829b feat(migrate): add --schemas param to prisma db pull (#17034)
• b3963d5 feat: directUrl support (#17210)
• 06c00b2 fix(*): change datasource printing for multiSchema + cleanup (#16868)
• a4f2989 feat: improve prisma db pull error message (#16956)
• d6c043f chore(deps): update jest (#16786)
• a3cdde6 chore(deps): update dependency @​types/jest to v29.2.4
• 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)