An attach record in the future failed the backup job at once, because
it would hold every instance as older than the plugin. A record a few
minutes ahead is also what a leadership change between controllers
whose clocks differ leaves behind after an attach that worked, and
failing then throws away a backup that would have run. Within that
margin the job now keeps waiting: the instances predate the record, so
the rollout check holds the backup, and the deadline counted from the
record is not spent by the wait. Only a record further ahead is taken
as corrupt and fails the job.
Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>