We've discovered scenarios in TSan testing where code which is fully protected by WiredTiger's read/write locks reports data races. This seems to come from insufficient instrumentation for TSan which primarily depends on C11 memory model constructs to interpret the code.

This ticket will add atomic operations with acquire and release semantics on the respected _wt_rwlock* calls to help TSan understand our lock behaviour.