The RWMutex benchmark directly calls lock/unlock on the LockManager.

This is undesirable for two reasons:

1. That's not how ResourceMutexes are acquired in production code, they go through the RAII object ResourceLock.
2. The LockManager is a private implementation detail of the Catalog and its synchronization.

Because of the above, this benchmark should be switched to use ResourceLock instead.