feat(perf): ORM-623 add cache for migration data

[FGoessler]

This PR improves the performance of the prisma migrate dev command by avoiding redundant shadow database work.

During the execution of prisma migrate dev Prisma creates a DatabaseSchema based of the list of existing migrations for up to 3 times. In most cases with the exact same input of migrations and hence same output of DatabaseSchema. This is a costly operation as it needs to apply the migrations to a shadow database. This becomes especially slow when connecting to a remote database like Prisma Postgres.

Prisma now caches this result after the first computation. There are still cases where the list of migrations provided as input can vary between the invocations. Hence the cache uses a hash of the provided migrations as cache key.

This implementation was a bit tricky as the DatabaseSchema struct and parts of the SqlDatabaseSchema (the ConnectorData) are type erased constructs. This made a simple clone impossible and I had to do some workarounds. Cloning is required so one variant of the DatabaseSchema can be stored in the cache while another clone can be passed on for further processing in the diffing process.

In my testing against Prisma Postgres this change decreased the runtime by ~50%. From ~2 minutes before my changes to now ~1 minute.

• ORM-623: Improve migration command performance
• Original investigation work on Notion.

[codspeed-hq]

CodSpeed Performance Report

Merging #5471 will not alter performance

_{Comparing feat/ORM-623-migrate-perf (bf7f7ce) with main (82e5178)}

Summary

✅ 11 untouched benchmarks

[github-actions]

WASM Query Engine file Size

Engine	This PR	Base branch	Diff
Postgres	2.188MiB	2.184MiB	4.407KiB
Postgres (gzip)	876.182KiB	875.160KiB	1.023KiB
Mysql	2.154MiB	2.149MiB	4.615KiB
Mysql (gzip)	861.318KiB	859.910KiB	1.409KiB
Sqlite	2.063MiB	2.058MiB	4.456KiB
Sqlite (gzip)	826.826KiB	825.455KiB	1.372KiB