Behavior was recently changed so that calling a catalog cache refresh with allowLocks: false no longer automatically throws an error.

The aim of this ticket is to find another way to bring about the error for this test case, or alternatively find a solid way to argue that we don't need the test case any longer, since the behavior has changed.

More context available in the linked BF, where tommaso.tocci found a place for a sleep that will constantly trigger the test case's failure.