Upgrade to more recent prisma versions - "warning prisma-dbml-generator > @prisma/internals > ...: This module is not supported"

[seaders]

We're getting to that time in the npm package cycle where many sub-packages are spewing warnings and potentially causing underlying problems. The below is caused by running against prisma 5x when it's all at 6x now.

warning prisma-dbml-generator > @prisma/internals > temp-write > uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning prisma-dbml-generator > @prisma/internals > @prisma/fetch-engine > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning prisma-dbml-generator > @prisma/internals > tmp > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning prisma-dbml-generator > @prisma/internals > tempy > del > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning prisma-dbml-generator > @prisma/internals > npm-packlist > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning prisma-dbml-generator > @prisma/internals > @prisma/fetch-engine > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning prisma-dbml-generator > @prisma/internals > archiver > archiver-utils > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning prisma-dbml-generator > @prisma/internals > archiver > zip-stream > archiver-utils > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning prisma-dbml-generator > @prisma/internals > npm-packlist > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning prisma-dbml-generator > @prisma/internals > @prisma/fetch-engine > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

I understand this is a fairly involved task though and will be happy to start a PR for this process, if you're open to it.