Utila vault transaction sync

Backstop for missed Utila webhooks, and the initial backfill. Each run walks one vault's on-chain transactions oldest-first, creating any that are missing, then asserts the feed was drained by comparing Utila's total against the stored count — a mismatch fails the run rather than leaving balances quietly wrong. Existing rows are never duplicated. One schedule per vault: a vault id is required, and prod has two (operating and custody).