Marks 0_init as applied via prisma migrate resolve so Prisma's migration history is in sync with the pre-existing conversion_jobs table, without running any SQL against the table itself.
