SERVER-139523Needs Scheduling

Provide ability to disable stack trace captures during tasserts in tests

Some tests might not care about tassert output but they pay a time cost for the stack trace capture that happens during it slowing them down considerably. For example bson spatial fuzz test doesn't care about tassert trips during fuzzing but it pays the time cost. I found a roughly 44x speed up if I disable libunwind but I found a 300x speed up if I disable stack trace collection altogether.

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.