The configsvr_commit_refine_collection_shard_key.js test directly calls _configsvrCommitRefineCollectionShardKey on the config server to test the metadata changes happening when refining a shard key.

While in production shards that call the command retry upon config server step-down, the test does not present any retry logic.

It doesn't make much sense to make the test resilient to stepdowns, hence we should simply blacklist it from stepdown suites by applying the does_not_support_stepdowns tag.