In our test setup there's logic to wait until we have a stable recovery timestamp during fixture setup. For DSC, we've been skipping the logic because no stable recovery timestamp was ever populated. 

In SERVER-132984, we're finally populating that timestamp. But we can't remove the skip quite yet because DSC multiversion suites will hang forever unless both the old and new nodes have that timestamp population. 

Therefore this ticket will track the removal of the skip, and can ONLY be done once a DSC release containing SERVER-132984 is published in the Atlas release feed.

Fix needs to be applied in two places. There's DisaggReplicaSetFixture._await_stable_recovery_timestamp and ReplicaSetFixture._await_stable_recovery_timestamp. (Note, these links are to master pre-SERVER-132984 merge. Links to be updated after merge.)