There is no coverage of write conflict exceptions in testing suites, which we learned as part of SERVER-126326. This led to changes across different codeowners where we didn't appropriately handle write conflict exceptions. Let's add setting WTWriteConflictExceptionChance so we can have coverage of ensuring appropriate write conflict exceptions handling in the config fuzzer suites.

One thing to note is that WTWriteConflictExceptionChance is a failpoint and not a server parameter, so will need different method of setting (although claude suggests):

  "failpoint.WTWriteConflictException": {
      "choices": [{"mode": "off"},
                  {"mode": {"activationProbability": 0.0001}},
                  {"mode": {"activationProbability": 0.001}}],
      "fuzz_at": ["startup"],
  },

Another thing to consider is that we also fuzz writeConflictRetryLimit with range [1, 20000]. We may want to make the range a bit higher (so [default, 20000]) to make sure these two fuzzed parameters don't completely fail the config fuzzer suites.

Also note that jstestfuzz does have both the WTWriteConflictException and WTWriteConflictExceptionForReads but doesn't run on jstest corpuses (will not actually run the jstest correctness passthroughs).