Currently there is one place where there is a lock order inversion in the BucketCatalog, where a caller tries to take a lock on the stats mutex while holding a lock on a bucket mutex. This leads to deadlock (and subsequently test timeouts) in jstests/concurrency/fsm_workloads/create_timeseries_collection.js. The underlying behavior should be fixed by SERVER-54985 which is currently under review. Until it is merged, we can simply disable the test and later re-enable it.