Based on the results of the Spike ticket linked, we have two things to do before we can start adding symbolized stack traces to shell outputs in Evergreen.

1. Fix the locking issue around how stacktraces were being found by the file system
2. Add a 5 minute timeout to how long we wait to try to get symbols and symbolize stacktraces. If it takes longer than that, we gracefully fail the symbolizer and allow the task to continue

------------------------

As a Server engineer,

I want to see symbolized tracktraces in my Evergreen logs,

so that I can easily debug my failures.

------------------------

AC:

• Symbolized stacktraces will be shown at the end of the test log they appear in
• If we can't symbolize a task, we gracefully fail the symbolizer portion of the task and allow the task to continue on like normal