Add ability to set Prisma connection_limit for each deployment separately

Some deployments using the same backend don't really need the same amount of connections in the pool. Don't know how this is actually affecting anything, but anyway.

Possibly need to pass the full connection string, as Prisma schema needs to be able to access the env value directly. 
