SERVER-91668 contains a description of why TransactionParticipant::checkStatementExecuted is expensive.

In all existing usages of the function where we want to know if a specific statment has been executed but we don't need to retrieve the oplog entry associated to the statement we can replace the function with the more performant TransactionParticipant::checkStatementExecutedNoOplogEntryFetch.

Currently, I see 3 candidates for this improvement:

•  _runAggregate()
• checkRetryableDDLStatementExecuted (global_index.cpp)
• resharding