fix: use in-memory startedAt for cron job log to survive DB restore

The auto-import wipes the database, destroying the cronJobLog record
created at the start of the job. Now duration is calculated from a
local variable instead of querying the DB, and if the record is gone
a fresh log entry is created in the restored database.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

packages/db/generated/prisma/index-browser.js

@@ -125,7 +125,9 @@ exports.Prisma.UserScalarFieldEnum = {
   username: 'username',
   password: 'password',
   autoBackupEnabled: 'autoBackupEnabled',
-  usbBackupEnabled: 'usbBackupEnabled'
+  autoBackupHour: 'autoBackupHour',
+  usbBackupEnabled: 'usbBackupEnabled',
+  usbBackupHour: 'usbBackupHour'
 };
 
 exports.Prisma.PatientScalarFieldEnum = {