This stops the trace exporter thread as well, preventing potential issues from the exporter thread running after tracing itself has been shutdown. This was found while investigating [BF-44775](https://jira.mongodb.org/browse/BF-44775), and theoretically could be the cause but I tried reproducing it in an integration test but wasn't successful. However, this change still makes the code more correct and robust.