Exclude prisma from serverless functions

[pi0neerpat]

The Prisma client is incorrectly being added to every function. For example, only 3 of the 7 functions below import the db object. This can be a big problem for hitting the serverless size limit. Its also an inefficient use of resources. Prisma should only be included if needed

To reproduce:

yarn rw build api && \
yarn zip-it-and-ship-it api/dist/functions/ zipped

Related to #2250 and #1196

[jtoar]

Thanks @pi0neerpat. I also see prisma in the node_modules of a zipped function that doesn't use it at all. I'll keep investigating when time permits, but in the meantime, @dac09 @thedavidprice thoughts on this one?

[thedavidprice]

If this is the case, we need to confirm with Netlify team and loop in Prisma team. Netlify owns ZiSi and will need to modify. (Also, not sure if this is a side-effect from them using ESBuild, which has been the cause of previous problems.)

@pi0neerpat We've switched to using Vercel's NodeFileTrace, which you can see in use for our Serverless deploy command here:
https://github.com/redwoodjs/redwood/blob/main/packages/cli/src/commands/deploy/packing/nft.js