Currently, the orphanCleanupDelaySecs value is not persisted across step downs; therefore this parameter is reset to the original value every time a step-down/step-up occurs and enqueued range deletions have to wait for the same amount of delay again.  If the orphanCleanupDelaySecs is set to a very high number (eg a week) and elections occur, the enqueued range deletions never get processed.

We must capture and persist the time to process a rangeDeletion request (i.e. record the time the request comes in + orphanCleanupDelaySecs) and use this timestamp to understand when we can start the range deletion.