Improve Stack Traces for $transaction

Bug description

When running this:

const transactionUpdate = prisma.transaction.create({
	data: {
		// ...
		amount: amount,
		user: {
			connect: {
				id: userId,
			},
		},
	},
})

const userUpdate = prisma.user.update({
	where: { id: userId },
	data: {
		balance: {
			increment: amount,
		},
	},
})

await prisma.$transaction([transactionUpdate, userUpdate])

when amount is unset, it results in the following error:

Error: Error in query graph construction: QueryParserError(QueryParserError { path: QueryPath { segments: ["Mutation", "createOneTransaction", "data", "TransactionCreateInput", "amount"] }, error_kind: RequiredValueNotSetError })
    at /Users/luca/projects/ws-backend/node_modules/@prisma/client/runtime/index.js:27330:19
    at processTicksAndRejections (node:internal/process/task_queues:93:5)

This is really frustrating since I have no idea where in my code this error occurred.

It works fine when I run it individually using await. This just happens when using with $transaction.

How to reproduce

Expected behavior

Prisma information

Environment & setup

• OS:
• Database:
• Node.js version:
• Prisma version: 2.13.0

@prisma/cli          : 2.13.0
@prisma/client       : 2.13.0
Current platform     : darwin
Query Engine         : query-engine 833ab05d2a20e822f6736a39a27de4fc8f6b3e49 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 833ab05d2a20e822f6736a39a27de4fc8f6b3e49 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 833ab05d2a20e822f6736a39a27de4fc8f6b3e49 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 833ab05d2a20e822f6736a39a27de4fc8f6b3e49 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Studio               : 0.329.0
✨  Done in 2.60s.

[eduhenke]

We are needing this because we are integrating with an APM solution, and all queries we perform have a .$transaction wrapped in them(because we also need RLS-support)

[ghost]

Note that Prisma does have the stack trace of the call site. It could potentially add to the Error object. It does already add some information in dev mode: https://github.com/prisma/prisma/pull/8646.