@@id([providerId, accountId]) the error goes away when I replace this with a new id field/column in schema.prisma, but this would be a risky migration to run on a production database (it would break all existing references to the Account table). Are there any other solutions? Has anyone successfully migrated a production app from next-auth to better-auth?