transactions_stale_shard_version_errors.js attempts to provoke a StaleConfig exception inside a transaction by blocking catalog cache refreshes on a specific shard.

On CSRS stepdown suites blocking the catalog cache refreshes after the migration it is not enough to cause the StaleConfig exception. In fact the CSRS on stepUp execute the PeriodicShardedIndexConsistencyChecker that in turn it triggers a refresh on the shards. So if this happens after the test has migrated the chunk but before test test had stopped the refreshes on the shard, the transaction would succeed.

For this reason we should blacklist this test from the CSRS stepdown suite.