Split the prisma cli in multiple packages

Problem

A lot of my clients are running prisma migrations at runtime when the service boots. While I don’t recommend this approach, this is what they do. This leads to an annoying problem where they either include all dev dependencies in their production Docker image or they add the full prisma cli in the production dependencies. This bloats the image unnecessarily.

Suggested solution

It would be nice if we could just add a smaller @prisma/migrate package in the production dependencies that would only contain the commands necessary to perform the migrations.

Alternatives

Continue doing what they are doing or have another step in the CICD to do the migration (should be preferred but hard to make happen sometimes)

[Sytten]

Depends on the company:

• Organizational -> getting approvals to do the changes, infrastructure team needs to change the process, etc
• Technical -> database is in a private VPC and it would thus require a second image to do the migration
• Security -> Not all cicd pipeline have an approval process built-in to execute the migration
• They do production deployments manually and thus they dont have CD

[jcpage]

Ok - I think my issue is highly related to this improvement (the goal is the same - to have a small amount of code specific to migrations) and I think the download code is technically behaving as designed - but I’ll open a new one that is more specific.

(filed as #11234 )