Using resmoke's config fuzzer on a test that calls MongoRunner.runMongod is not an operation with a clear outcome:

 - On the one hand, at time of writing, it has the expected behaviour, i.e. that configurations generated by the fuzzer will be applied to invocations of MongoRunner.runMongod().

 - On the other hand, it is an invalid use of resmoke, as those tests are written with the assumption that they have full control of the invocation, and allowing the fuzzer to change those invocations will probably break many tests.

The invalidity of that operation becomes an issue in the face of SERVER-92148, because new configs will be added that do not take effect in runMongod() invocations. At that point, fuzzing runMongod() invocations will go from being a questionable thing to do (which happens to work), to an actually incorrect thing to do (because resmoke isn't moving all of its fuzzed configs into runMongod() calls).

For that reason we will enforce the understanding that fuzzing runMongod() invocations is wrong, by crashing tests that try to do it.