Add configuration to disable query batching

[janpio]

Sometimes our batching functionality (see https://www.prisma.io/docs/orm/prisma-client/queries/query-optimization-performance#solving-n1-in-graphql-with-findunique-and-prisma-clients-dataloader) does not work as intended (see for example bugs with label topic: batching).

Right now, there is no way for our users to opt out of that functionality.
We should add one, disableQueryBatching: true or findUniqueBatching: false could work in some form.

[ericallam]

Would definitely be nice to be able to do this, as it recently caused outage on trigger.dev by doing a full table scan. ref: https://twitter.com/maverickdotdev/status/1800178147897561317