Necessary for `prisma dev`:
https://github.com/prisma/team-expansion/pull/1903/files#r2322689633

Part of
https://linear.app/prisma-company/issue/TML-1317/add-qc-support-in-local-ppg-with-accelerate-api

…tring (#28261)

MultiSubnetFailover is a SQL Server connection property that enables
faster failovers for Always On Availability Groups and Failover Cluster
Instances, whether across single or multiple subnets. When enabled,
clients connecting to a SQL Server listener will attempt to connect to
all its IP addresses simultaneously, choosing the first one that
responds, which significantly reduces reconnection time after a failover
event.

The Tedious package [supports it as an
option](https://github.com/tediousjs/tedious/blob/ebb023ed90969a7ec0e4b036533ad52739d921f7/src/connection.ts#L756),
however to use it from a connection string it needs to be extracted.

Ref #9187

---------

Co-authored-by: jacek-prisma <malec@prisma.io>

this PR introduces PNPM catalog to ease dependency version management.
https://pnpm.io/catalogs

This reverts commit 10fab6b.

This reverts the inclusion and usages of pnpm catalog. The reason for
reverting the change is that it breaks the prisma-engines test pipeline
(see
https://github.com/prisma/prisma-engines/actions/runs/18382915995/job/52373895545)
and we have no simple fix for it.

…#28268)

- Bump `@opentelemetry/*` packages.
- Align tracing functional tests with the latest SDK APIs.
- Update `@prisma/instrumentation` README examples to match the new
configuration patterns in `@opentelemetry/sdk-trace-base@2`.

Part of
https://linear.app/prisma-company/issue/TML-1317/add-qc-support-in-local-ppg-with-accelerate-api

…3ff8dbb0424 (#28258)

The base branch for this PR is: main
This automatic PR updates the engines to version
`6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0424`.
This will get automatically merged if all the tests pass.
:warning: If this PR needs to be updated, first remove the `automerge`
label before pushing to avoid automerge to merge without waiting for
tests.
## Packages
| Package | NPM URL |
|---------|---------|
|`@prisma/engines-version`|
https://npmjs.com/package/@prisma/engines-version/v/6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0424|
|`@prisma/prisma-schema-wasm`|
https://npmjs.com/package/@prisma/prisma-schema-wasm/v/6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0424|
|`@prisma/query-engine-wasm`|
https://npmjs.com/package/@prisma/query-engine-wasm/v/6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0424|
|`@prisma/query-compiler-wasm`|
https://npmjs.com/package/@prisma/query-compiler-wasm/v/6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0424|
|`@prisma/schema-engine-wasm`|
https://npmjs.com/package/@prisma/schema-engine-wasm/v/6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0424|
## Engines commit

[`prisma/prisma-engines@b03d75f1a67e62289420f5697c28a3ff8dbb0424`](prisma/prisma-engines@b03d75f)

Export the package version as a named export from
`@prisma/query-plan-executor`. This is necessary for the
`Prisma-Engine-Hash` header validation to work in `prisma dev`.

Part of
https://linear.app/prisma-company/issue/TML-1317/add-qc-support-in-local-ppg-with-accelerate-api

Initialize the OpenTelemetry SDK in the CLI entrypoint to make it usable
in loadable sub-commands. Since they are libraries, they should not be
initiaizing the SDK, it should be done by the application (the CLI).

Part of
https://linear.app/prisma-company/issue/TML-1317/add-qc-support-in-local-ppg-with-accelerate-api

…e94bfda7624 (#28288)

The base branch for this PR is: main
This automatic PR updates the engines to version
`6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7624`.
This will get automatically merged if all the tests pass.
:warning: If this PR needs to be updated, first remove the `automerge`
label before pushing to avoid automerge to merge without waiting for
tests.
## Packages
| Package | NPM URL |
|---------|---------|
|`@prisma/engines-version`|
https://npmjs.com/package/@prisma/engines-version/v/6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7624|
|`@prisma/prisma-schema-wasm`|
https://npmjs.com/package/@prisma/prisma-schema-wasm/v/6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7624|
|`@prisma/query-engine-wasm`|
https://npmjs.com/package/@prisma/query-engine-wasm/v/6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7624|
|`@prisma/query-compiler-wasm`|
https://npmjs.com/package/@prisma/query-compiler-wasm/v/6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7624|
|`@prisma/schema-engine-wasm`|
https://npmjs.com/package/@prisma/schema-engine-wasm/v/6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7624|
## Engines commit

[`prisma/prisma-engines@9bf76dbea6c9e34d59a3577015bd1e94bfda7624`](prisma/prisma-engines@9bf76db)

This PR:
- closes
[TML-1476](https://linear.app/prisma-company/issue/TML-1476/pgadapter-corrupts-historical-dates-with-2-digit-years)
- closes #28192

---------

Co-authored-by: jkomyno <12381818+jkomyno@users.noreply.github.com>
Co-authored-by: Jacek Malec <malec@prisma.io>

…179a39ccf48 (#28293)

The base branch for this PR is: main
This automatic PR updates the engines to version
`6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39ccf48`.
This will get automatically merged if all the tests pass.
:warning: If this PR needs to be updated, first remove the `automerge`
label before pushing to avoid automerge to merge without waiting for
tests.
## Packages
| Package | NPM URL |
|---------|---------|
|`@prisma/engines-version`|
https://npmjs.com/package/@prisma/engines-version/v/6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39ccf48|
|`@prisma/prisma-schema-wasm`|
https://npmjs.com/package/@prisma/prisma-schema-wasm/v/6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39ccf48|
|`@prisma/query-engine-wasm`|
https://npmjs.com/package/@prisma/query-engine-wasm/v/6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39ccf48|
|`@prisma/query-compiler-wasm`|
https://npmjs.com/package/@prisma/query-compiler-wasm/v/6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39ccf48|
|`@prisma/schema-engine-wasm`|
https://npmjs.com/package/@prisma/schema-engine-wasm/v/6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39ccf48|
## Engines commit

[`prisma/prisma-engines@d3fc122f88ca3ce86f67a797debfb179a39ccf48`](prisma/prisma-engines@d3fc122)

The bug happens because of our cache, which currently ignores the
provider in use


[TML-1503](https://linear.app/prisma-company/issue/TML-1503/fix-usage-of-multiple-prisma-clients-with-different-providers)

Fixes #28221

This PR:
- closes
[TML-1332](https://linear.app/prisma-company/issue/TML-1332/prisma-config-alternative-to-url-directurl-shadowdatabaseurl)
- this PR depends on prisma/prisma-engines#5645.

---------

Co-authored-by: jkomyno <12381818+jkomyno@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Conflicts were automatically solved using [Mergiraf](https://mergiraf.org)