Add a max delay bound for column reconstruction to avoid indefinite waiting on staggered gossip

[jimmygchen]

There was a recent optimisation made to delay reconstruction
#7588

It has shown to be quite effective at improving supernode performance, however we should consider having a maximum delay on performing reconstruction. Reconstruction is currently triggered once we have at least 64 columns, and not received any more gossip columns for 150ms:

lighthouse/beacon_node/beacon_processor/src/scheduler/work_reprocessing_queue.rs

Line 59 in f67084a

pub const QUEUED_RECONSTRUCTION_DELAY: Duration = Duration::from_millis(150);

In the case where gossip columns arrives in a staggered manner (e.g. 100ms between columns from 64 to 70), it could delay reconstruction too much, and this should be a scenario to prevent against.