We have a case where the step-up thread gets automatically recruited by WiredTiger's eviction server to help ease cache pressure, but can't make any progress and hangs (see WT-17718 for details).

This is because eviction can't make progress until the stable timestamp advances, which depends on the step-up thread's commit completing, so we have a self-deadlock.

The proposed solution is to use the setNoEvictionAfterCommitOrRollback() API to exempt the step-up thread from being pulled into cache eviction, thus preventing the deadlock.