fix(client): prune generated dmmf

[millsp]

This PR prunes the generated dmmf in the client to its bare minimal version, and only does it when we are generating the wasm client. This improves gzip compression.

[github-actions]

size-limit report 📦

Path	Size
packages/client/runtime/library.js	193.76 KB (0%)
packages/client/runtime/library.d.ts	81 B (0%)
packages/client/runtime/binary.js	604.84 KB (0%)
packages/client/runtime/binary.d.ts	26 B (0%)
packages/client/runtime/edge.js	182.45 KB (0%)
packages/client/runtime/edge-esm.js	182.35 KB (0%)
packages/client/runtime/wasm.js	204.7 KB (+0.01% 🔺)
packages/client/runtime/index-browser.js	33.5 KB (0%)
packages/client/runtime/index-browser.d.ts	89 B (0%)
packages/cli/build/index.js	2.71 MB (0%)
packages/client/prisma-client-0.0.0.tgz	1.43 MB (+0.02% 🔺)
packages/cli/prisma-0.0.0.tgz	3.9 MB (+0.01% 🔺)
packages/bundle-size/da-workers-libsql/output.tgz	963.63 KB (-0.35% 🔽)
packages/bundle-size/da-workers-neon/output.tgz	987.92 KB (-0.34% 🔽)
packages/bundle-size/da-workers-pg/output.tgz	1009.65 KB (-0.34% 🔽)
packages/bundle-size/da-workers-planetscale/output.tgz	938.08 KB (-0.36% 🔽)
packages/bundle-size/da-workers-d1/output.tgz	933.47 KB (-0.36% 🔽)

[SevInf]

Do we know if that will affect any of the third party projects? runtimeDataModel itself is private, but is also used to re-create Prisma.dmmf.

[millsp]

This change only targets wasm build. So to your point, I think we should at least throw an error for Prisma.dmmf there, as it may only be partially true otherwise?

[SevInf]

Yes, i think error for Prisma.dmmf would be an ok way to go, if it is only about wasm build

[alexdoan102]

@millsp @SevInf @hayes since prisma now support cloudflare
==> https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-cloudflare

we need the Prisma.dmmf to use with 3rd party [@pothos/plugin-prisma] plugin.
==> this is the issue: hayes/pothos#1190

can you  please put this property back, so that the graphql plugins will work for edge./cloudflare?