Due to SERVER-37841, multi_statement_transaction_all_commands.js implicitly aborts transactions. When glabal writer lock is enqueued after a running transaction, higher txnNumber will block while waiting for read concern's afterClusterTime, since it needs the lock to access the oplog collection. Waiting for read concern is moved to before implicitly aborting transaction by SERVER-37179.

Once SERVER-37841 is done, we can unblacklist it in concurrency_simultaneous_replication.

Additionally, until SERVER-37199 is fixed, multi_statement_transaction_atomicity_isolation_metrics_test.js is also blacklisted in the concurrency_simultaneous_replication test due to a deadlock caused by secondary application of prepared transactions. This ticket should also unblacklist multi_statement_transaction_atomicity_isolation_metrics_test.js once this is fixed.