lock_stats.js essentially tests that the time spent trying to acquire a lock is correctly calculated and does so by setting an upper and lower bound on this count. However, it relies on no other operations running in parallel while it is running, which occasionally causes the test to fail. We can make testing this behavior less flaky by instead checking for the same property within a unit test. There is already some existing coverage of this behavior in lock_stats_test.cpp.