Shards can now have transaction router for a transaction. This means it can leave transactions dangling on other shards if it gets killed while the transaction is in progress. This wouldn't be an issue for default settings because the transactions will eventually die. But we set transactionLifetimeLimitSeconds to be very high on some tests and this would cause it to live very long causing conflicts on other tests (like when fsync is called in some of the post test hooks)