[EXPORTER] OTLP HTTP exporter should not detach threads

[marcalff]

Context

In an instrumented application, the opentelemetry-cpp library static library is linked inside a bigger shared library, loaded and unloaded dynamically.

On cleanup, the code:

• calls shutdown on every signal provider
• releases the last references to every signal provider
• unload the shared library

Problem

The OTLP HTTP exporter background threads are detached, and may still run by the time the shared library is unloaded.

This causes the code of the opentelemetry-cpp library itself to be un mapped from the process space, while a thread is still running, leading to a crash.

Expected behavior

Never detach a thread.

Instead, properly join background threads to make sure the cleanup is complete, before returning from Shutdown.

This affects the OTLP HTTP exporter, as well as the OTLP FILE exporter.

[owent]

Currently, if we don't detach background threads, std::thread resources are only freed during subsequent API calls to OtlpFileSystemBackend and HttpClient. This causes resource will not be freed until these APIs aren't called again.
Is there a better solution for managing these thread resources?