fix(prisma): reconcile schema drift, indexes, and migration timestamps (#1617)

[Awosdot]

What changed

• Reconciled schema drift on the Transaction model and updated src/vaultEndpoints.ts to align model property access with Prisma definitions[cite: 13].
• Added @@index([status, nextRetryAt]) to EmailQueue in prisma/schema.prisma and cleaned up redundant index declarations[cite: 13].
• Created corresponding SQL migration and rollback scripts under prisma/migrations and prisma/rollbacks[cite: 13].
• Renamed duplicate migration timestamps and disambiguated colliding migration folder names[cite: 13].

Why

Schema field mismatches caused runtime type errors, while missing indexes degraded email queue processing performance[cite: 13]. Duplicate migration folder timestamps broke automated migration tracking in CI[cite: 13].

How tested

• Ran npx prisma validate and tsc --noEmit to confirm zero schema or TypeScript errors[cite: 13].
• Verified node scripts/check-migrations.js passes cleanly[cite: 13].

Closes

Closes #1617

[drips-wave]

@Awosdot Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits