reap_sessions_with_active_yielders.js tests that if a logical session expires while a transaction router is yielded, that prevents reaping the in-memory transaction state for that router's session. It simulates expiration by manually deleting from config.transactions with the default write concern, which can trigger the scenario from SERVER-92718 if a logical session cache refresh later reads from a stale secondary and does not see the deletion. The test is failing frequently enough and isn't meant to test the logic in SERVER-92718, so we should avoid failures by making it wait for the manual delete to replicate to all nodes before continuing the test.