Disable merge_with_move_primary.js from running on the sharding_csrs_continuous_config_stepdown suite

This test executes several movePrimary commands. The problem appears when the CS primary node steps down during the execution of one of them: the movePrimary may continue its execution on the shards and once the new CS primary node is elected we may end up having two move primary commands being executed at the same time over the same database (the distributed lock is released once the CS primary node is elected).