With the work done in order to enable having additional participants in multi-shard transactions we can end up in a situation where the following happens for a given session:

• Operation 1 (Op1) reads some documents from a local WT cursor via DocumentSourceCursor
• Op1 then performs a remote call and checks in the session + transaction resources to prevent a deadlock
• The node then receives an abort transaction command (Operation 2)
• Op2 checks out the session and we end up in a situation where both Op1 and Op2 have resources for the transaction

To avoid this we should make sure we do not hold any resources after reading the data. This way we can maintain the invariant that only one operation at a time has full ownership of the session and its resources.