In sharded clusters, some background operations can cause write conflicts that would increment a server status counter, making an assert in transaction_write_conflicts.js fragile.

This doesn't happen regurally, but with an additional complexities on TSAN and disagg combined, the test is much more flaky.

To address this, the test will check server statuts counters just for GTE rather than EQ, but to keep test coverage, in additiona to server status checks, the test is also checking logs to see write conflict counters for specific transactions.