This test must not run in config stepdown suites because it can happen that:

• Inserts happen, the ChunkSplitter triggers a new split task on the shard
• The CSRS primary steps down
• The split commit fromthe ChunkSplitter gets delayed waiting for a new CSRS primary
• More inserts happen on the shard, but the split driver is still busy waiting for the previous commit, so no new split is triggered
• The new CSRS primary steps up, serving the original split commit