Currently, when the parameter gWiredTigerStressConfig is enabled, we simulate stress in WT via the history_store_checkpoint_delay and checkpoint_slow testing params that WT exposes.

However there are a bunch of other params like WT_TIMING_STRESS_PREPARE_CHECKPOINT_DELAY, WT_TIMING_STRESS_HS_CHECKPOINT_DELAY, WT_TIMING_STRESS_CHECKPOINT_STOP, WT_TIMING_STRESS_CHECKPOINT_HANDLE, etc. that we could use to simulate slowness / stress.

We could consider turning these on.

Even better would be to have these be fuzzed themselves so that they don't take on values of just {0, K} as they do now, and instead pick randomly from a range [0, K]. This would also help prevent the all-or-nothing testing we currently have, where the stress params are all turned on or all turned off.