SERVER-139112ClosedFixed
Live references to tables when a replicated drop is being applied should not be a fatal error
In the normal flow a replicated table drop should only be applied after the oldest timestamp has advanced past the drop timestamp, and so there should not be any remaining readers pinning the table. We therefore chose to make this a fatal error, as it's most likely not a transient condition and it's better to just restart a secondary than stall replication forever. Magic Restore turns out to be an exception to this. The collection drop and table drop can be applied with no delay, and while mo