chore(deps): update engines to 5.19.0-31.5fe21811a6ba0b952a3bc7140066…

…6511fe3b902f (prisma#25088)

chore(config): migrate renovate config (prisma#24956)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

feat(cli, generate command): Added promo array to rotate and make cli…

… messaging more engaging (prisma#24792)

* Added promo array and modified the existing promo text in the generate file

* removed the boxed message and promo from init command and added an adittional step

* updated tests and snapshot with mocked sample tip

* Added Tip: keyword at the beginning of the 5th step in prisma init command

* updated iinit command snapshots

* update snapshots for generate command

* snapshots

* Added missing links and updated snapshots

* remove whitespace

* updated snapshots

fix(client): Fix vercel edge middleware bundling. (prisma#24730)

This reverts the fix introduced in prisma#24554 and adds alternative fix for
`vitest` problems. Original fix introduced the regression (prisma#24673).

After debugging `vitest` and `@clodflare/vitest-pool-workers`, what I
found out is that despite what error message, reported in prisma#23911 says,
`vitest` can correctly resolve `#wasm-engine-loader` module, however,
later it tries to load it as common.js module and fails. on `export`
syntax.

[Relevant `@cloudflare/vitest-pool-workers` code](https://github.com/cloudflare/workers-sdk/blob/86799718836d65526ff0c6b16729c16d7fa1d351/packages/vitest-pool-workers/src/pool/module-fallback.ts#L453).

Switching the extension of the wasm loader to `.mjs` fixes vitest
without breaking vercel edge middleware.

Fix prisma#24673

fix(client): restore loading `.env` files in `@prisma/client` (prisma…

…#24649)

* chore: set minimum compilation target to ES2021 (>= Node.js 16.4.x)

* fix(client): fix loading .env files wrt generator output

* Revert "chore: set minimum compilation target to ES2021 (>= Node.js 16.4.x)"

This reverts commit 10a7969.

* test(client): add e2e test for prisma#24634

chore(deps): update engines to 5.16.0-24.34ace0eb2704183d2c05b60b52fb…

…a5c43c13f303 (prisma#24625)

chore(deps): update engines to 5.15.1-1.5675a3182f972f1a8f31d16eee6ab…

…f4fd54910e3 (prisma#24561)

chore(tests): Remove `providerFeatures` from functional test example …

…and docs (prisma#24402)

feat(schema-files-loader): Customize file loading logic (prisma#24085)

* feat(schema-files-loader): Customize file loading logic

Allows to swap files resolution logic used by the package.
By default, package still uses real fs (see `realFsResolver`).
Additinal implementatins are:

- `InMemoryFilesResolver` as the name suggests, keeps virtual file tree
in memory.
- `CompsoiteFilesResolver` combines two resolvers together.

Both will be used for language-tools, where some of the source files
might diverge from their on-disk content while editing.

Contribute to prisma/team-orm#1042

* Windows, why are you like this

* Build correct file

* Handle case-sensitivity

* Check preview feature when looking up related files

* Fix formatting

* Finish writing comment

* Split paths by either slash

* Unbreak lockfile

* Split by path better

chore(deps): update engines to 5.13.0-23.b9a39a7ee606c28e3455d0fd60e7…

…8c3ba82b1a2b (prisma#23916)