fix: wait the full hour and keep Hold for automatic owed-plugin retries on a schedule (#201355)

* fix(update): keep the owed-plugin retry cooldown and hold on cron schedules

With update.auto.schedule set, the owed-plugin retry measured its one-hour
cooldown against the current cron window, so a five-minute schedule could
restart the Gateway minutes after the automatic update that installed the
version. A later check outside the window also retired an announced retry,
so a held retry never resumed.

The retry now gates new campaigns on elapsed time since that attempt, and a
check that still finds the row owed keeps an announced campaign, including
its hold. The ledger still bounds each owed row to one retry per version.

* test(update): keep owed-plugin retries inside cron windows after the cooldown

* test(update): prove the owed-plugin retry cooldown through a scheduled managed Gateway

* test(update): report the schedule cell's phases and compare retry versions

* test(update): drop the unfinished schedule Docker cell