Recently a TSan related change caused a fairly regular segmentation fault error in a number of tests, this wasn't picked up in WiredTiger testing as we never run TSan on tests that is isn't ready for yet.

If we run TSan on tests that it isn't ready for it will correctly dump a load of TSan errors and the test will fail. If we can work around this we can create a temporary variant in evergreen that will run TSan, not catch TSan error but catch any other logic error that TSan changes may introduce.

Scope:

• Create new variant and have it run successfully ignoring TSan warnings