Currently we are checking this invariant when setting the stable timestamp..

It is suspected that we can fetch a stale value for the all durable timestamp because we lack strong synchronization, which could make this invariant fail under some circumstances even though all durable is really greater than the stable timestamp.

Given that WT already checks the same property both for prepared transactions and for non-prepared transactions with the appropriate synchronization we can remove the check at this layer.