Logs tables bloat caused by corrupted action schedules

The issue resurfaced in p1772090743156589-slack-C08SVLULL3B: A-S built-in migration can potentially cause schedule data corruption (serialized data gets truncated), and A-S will keep trying to process it, spawning more logs.