This test is currently disabled in all sharding concurrency suites since those suites use sharded cluster with two routers and this test makes all threads run commands in same transaction. That is, with multiple routers, the transaction cannot be committed since the participant list on each router is incomplete. While that makes sense, it is useful to test having multiple threads using the same session on a sharded cluster with embedded router since on an embedded router when the AsyncRequestSender always yield the session before it sends out the requests to shards. Having multiple threads using the same session can lead to interleaving that may uncover issues that we missed.