We are currently writing all traces files to the ${workDir}/build/OTelTraces directory for all tests. Evergreen automation will attempt to ingest all files written to this directory into Honeycomb. There are drop rules for Honeycomb to drop all spans with the attribute `DROP_SPAN` set to true.

We have a flag in the server code for Spans to default this to true, so we have to explicitly set this on Span initialization if we want to keep the span in Honeycomb.

Even with minimal span coverage in the server code we are sending too many spans to Honeycomb.

The goal of this ticket is to limit the files written to ${workDir}/build/OTelTraces to just trace files relevant to specific test failures.

The general idea is:

• - Mongo process write traces files to a specific directory, maybe subdirectory of build/OTelTraces. Some naming scheme will exist to map a test to this subdirectory?
• A new? script will move files from the each failed test subdirectory to build/OTelTraces.
• Evergreen automation only uploads traces for failed test, we still have all tracing data available for download.

We are not adding this to SPM-1514 as it is not necessarily needed for project close out.