Prisma schema can't represent every type of postgres object, thus some migrations require custom SQL. At the same time, sometimes large amounts of migrations require squashing. I havent been able to find a way of squashing migrations will retaining the information from my custom SQL migrations. Right now I have my Prisma managed migrations in one folder, and custom sql migrations in another. Is this the canonical way of managing the two? Thank you.