In the BF, as part of the generated js test, we set the default write concern to be j: true, even though it's running on an inmem variant. This is ok in the generated js test since we wrap all top level statements in a try-catch. However, in the hooks that run after each generated test, we first run the the RunQueryStats hook, which then fails because we can't use j: true on an inmem variant. The issue is that the RunQueryStats hook comes before the FuzzerRestoreSettings hook here. The FuzzerRestoreSettings hook resets the default write concern (to remove j: true), so we should change the order of these hooks in the .yml file