fix: Prisma $queryRaw MySQL type coercion for BigInt and Boolean

$queryRaw on MySQL returns BigInt for integer columns and 0/1 for booleans.
Passing these raw values back to Prisma client methods causes validation errors:
- Expected Int, provided BigInt
- Expected Boolean, provided Int

Fixed in auth refresh, TOTP login, and TOTP backup code flows by wrapping
storedToken.id, storedToken.user_id with Number() and remember_me with Boolean().

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

src/routes/admin/totp.ts

@@ -282,8 +282,12 @@ export default async function totpRoutes(
           return { error: "Neplatný nebo expirovaný login token", status: 401 };
         }
 
+        // $queryRaw on MySQL may return BigInt for integer columns
+        const storedTokenId = Number(storedToken.id);
+        const storedUserId = Number(storedToken.user_id);
+
         const user = await tx.users.findUnique({
-          where: { id: storedToken.user_id },
+          where: { id: storedUserId },
           include: { roles: true },
         });
 
@@ -315,7 +319,7 @@ export default async function totpRoutes(
           const newFailedAttempts = (user.failed_login_attempts ?? 0) + 1;
           if (newFailedAttempts >= settings.max_login_attempts) {
             await tx.totp_login_tokens.delete({
-              where: { id: storedToken.id },
+              where: { id: storedTokenId },
             });
             await tx.users.update({
               where: { id: user.id },