This test should be blacklisted because it creates a collection, calls movePrimary, then calls shardCollection and moves a chunk to the old primary (see the linked SERVER-31909).

Any other tests that do this should also be blacklisted from the config stepdown suite.

Note: Many of our other tests do call enableSharding, ensurePrimaryShard, then shardCollection and moveChunk. But they don't
create any collections before calling ensurePrimaryShard (and neither enableSharding nor ensurePrimaryShard cause collections to be created). So I don't expect those other tests to fail in this way (i.e., not clean up a collection on an original primary, leading to a UUID inconsistency).