Multi statement transaction concurrency suites run each state function inside a transaction that's auto-retried.

The random_moveChunk_update_shard_key.js workload itself attempts to update shard keys in either a retryable write or transaction. It doesn't make sense from a high level to run either update scenario in a higher level transaction. This is both unexpected and could lead to odd error scenarios (see the linked BF). We should blacklist this workload from multi statement transaction suites.