If the distributed lock pinger runs after stopping replication and before the insert into the config database, the optime will be bumped and the insert will hang waiting for the higher optime to be replicated. This has happened on slower variants causing the test to timeout. We should disable the dist lock manager similar to what is done in readConcern_atClusterTime_noop_write.js