Coredumps when the OpenTelemetry collector host is unavailable.

Describe your environment
OpenTelemetry sdk: v1.8.1
Nginx: v1.21.6
Ingress-Nginx: v1.8.4
k8s: 1.24.6

Steps to reproduce

• HIghload Nginx.
• The collector's OpenTelemetry host is unavailable.

What is the expected behavior:
The absence of Coredumps when the OpenTelemetry collector host is unavailable.

What is the actual behavior:
Coredumps files are created

Additional context
Example Coredump:

(gdb) backtrace full
#0  0x00007fb00cc99b8a in opentelemetry::v1::exporter::otlp::OtlpGrpcExporter::Export(opentelemetry::v1::nostd::span<std::unique_ptr<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >, 18446744073709551615ul> const&) ()
   from /modules_mount/etc/nginx/modules/otel/otel_ngx_module.so
No symbol table info available.
#1  0x00007fb00cc91321 in opentelemetry::v1::sdk::trace::BatchSpanProcessor::Export() () from /modules_mount/etc/nginx/modules/otel/otel_ngx_module.so
No symbol table info available.
#2  0x00007fb00cc909c1 in opentelemetry::v1::sdk::trace::BatchSpanProcessor::DrainQueue() () from /modules_mount/etc/nginx/modules/otel/otel_ngx_module.so
No symbol table info available.
#3  0x00007fb00cc90b78 in opentelemetry::v1::sdk::trace::BatchSpanProcessor::DoBackgroundWork() () from /modules_mount/etc/nginx/modules/otel/otel_ngx_module.so
No symbol table info available.
#4  0x00007fb00c8711e3 in ?? () from /usr/lib/libstdc++.so.6
No symbol table info available.
#5  0x00007fb00de04bc2 in ?? () from /lib/ld-musl-x86_64.so.1
No symbol table info available.
#6  0x0000000000000000 in ?? ()
No symbol table info available.

Reproduce the high-load Nginx scenario with the OpenTelemetry collector host unavailable, then inspect OtlpGrpcExporter::Export and the BatchSpanProcessor::Export, DrainQueue, and DoBackgroundWork entry points shown in the backtrace. Done means the collector outage no longer creates coredump files.