#22911: fix(cron): correct next execution time calculation after gateway restart

## Summary Fix incorrect next execution time calculation for periodic (every N minutes) cron jobs after a gateway restart. ## Problem When a cron job that runs every 30 minutes restarts the gateway, the "next execution" time shown in the dashboard becomes incorrect. For example, if the last execution was 6 minutes ago, the next execution should be in 24 minutes (30-6), but it was showing 56 minutes instead. This occurred because the schedule calculation was using the current time as the default anchor point instead of the last execution time, causing it to calculate from an incorrect reference point. ## Solution 1. Modified `computeNextRunAtMs` in `schedule.ts` to accept an optional `lastRunAtMs` parameter 2. Updated the anchor calculation for "every" schedules to prioritize the last execution time: `lastRunAtMs ?? schedule.anchorMs ?? nowMs` 3. Updated all call sites in `service/jobs.ts` to pass `job.state.lastRunAtMs` to the function ## Fixes - Fixes #22895 <!-- greptile_comment --> <h3>Greptile Summary</h3> Fixed next execution time calculation for periodic cron jobs after gateway restart by passing `lastRunAtMs` to `computeNextRunAtMs` so it uses the last execution time as the anchor instead of current time. **Critical Issues Found:** - Missing semicolons on lines 35 (`schedule.ts`) and 87 (`jobs.ts`) - Missing closing brace `}` on line 87-88 (`jobs.ts`) - the function closing brace was accidentally deleted - Line 66 in `jobs.ts` also needs `lastRunAtMs` parameter to be consistent with the fix **Note:** These syntax errors will cause compilation failures and must be fixed before merging. <h3>Confidence Score: 0/5</h3> - This PR cannot be merged - it contains critical syntax errors that will prevent compilation - The PR has the right approach to fixing the cron scheduling issue, but contains multiple syntax errors: missing semicolons (lines 35, 87) and a deleted closing brace that breaks the function structure (line 87-88). Additionally, line 66 is missing the same fix applied elsewhere, creating inconsistent behavior. - Both `src/cron/service/jobs.ts` and `src/cron/schedule.ts` require immediate attention to fix syntax errors _{Last reviewed commit: af87151} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->