fix(error handling): ORM-439 map query error to user facing error so it propagates correctly

[FGoessler]

This PR fixes an issue where a generic QueryError would not propagate through our error handling all the way to the user. This lead to interactive transactions not failing (although they rolled back). Such QueryErrors happen in particular in case of failing DB triggers.

Fixes prisma/prisma#17303.

[FGoessler]

@jkomyno I had trouble finding a good spot to test this in the prisma-engines repo. Am adding an E2E test into the prisma/prisma repo for this instead (see prisma/prisma#26166). Or do you have a better idea / pointer for me? 🤔

[github-actions]

WASM Query Engine file Size

Engine	This PR	Base branch	Diff
Postgres	2.120MiB	2.120MiB	363.000B
Postgres (gzip)	848.694KiB	848.485KiB	214.000B
Mysql	2.083MiB	2.082MiB	363.000B
Mysql (gzip)	834.538KiB	834.396KiB	145.000B
Sqlite	1.990MiB	1.990MiB	353.000B
Sqlite (gzip)	798.228KiB	797.975KiB	259.000B

[codspeed-hq]

CodSpeed Performance Report

Merging #5135 will not alter performance

_{Comparing fix/ORM-439-interactive-transaction-failure (275a7e7) with main (2ad07dd)}

Summary

✅ 11 untouched benchmarks

[FGoessler]

Btw I am a bit worried about this line here. Because there is a looong list of errors that we do NOT map here and hence likely tend to swallow somewhere upstreams?

List of not mapped errors:

ErrorKind::ConnectionError(_) => {}
ErrorKind::InvalidConnectionArguments => {}
ErrorKind::ColumnReadFailure(_) => {}
ErrorKind::FieldCannotBeNull { .. } => {}
ErrorKind::DomainError(_) => {}
ErrorKind::RecordNotFoundForWhere(_) => {}
ErrorKind::RelationViolation { .. } => {}
ErrorKind::RecordsNotConnected { .. } => {}
ErrorKind::InternalConversionError(_) => {}
ErrorKind::DatabaseCreationError(_) => {}
ErrorKind::DatabaseDoesNotExist { .. } => {}
ErrorKind::DatabaseAccessDenied { .. } => {}
ErrorKind::AuthenticationFailed { .. } => {}
ErrorKind::RawApiError(_) => {}
ErrorKind::RollbackWithoutBegin => {}
ErrorKind::UnsupportedConnector(_) => {}
ErrorKind::InvalidDriverAdapter(_) => {}
ErrorKind::UnexpectedDatabaseVersion { .. } => {}

[FGoessler]

Actually seeing all the CI failures, I think I found a better an easier way to solve this issue. => Closing this PR.