Configurable max export delay value for OTLPExporterMixin

[avpps]

Description

Change related with #1842.

Default OTLPExporterMixin approach to retry exporting with hardcoded time range, causes issues when using it in short lasting processes and opentelemetry collector is not available.
Here is example where it "hangs" whole process execution: https://github.com/avpps/opentelemetry-python-examples/blob/master/examples/trace.py

I just moved hardcoded value to make it configurable. In my cases it make sense to not retry export at all.

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

OTLPExporterMixin tests pass after change.

Does This PR Require a Contrib Repo Change?

• No.

Checklist:

• Followed the style guidelines of this project

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: avpps / name: Piotr (36400f6, 0cd8bf0)
• ✅ login: ocelotl / name: Diego Hurtado (311d935)

[pmcollins]

Wondering if it makes sense for this to be a constructor argument with a default value, and for the name to reflect that it's a max backoff in seconds, so something like "max_backoff_seconds"?

[avpps]

Constructor argument will be convenient for local modifications, like (here with your proposed name):

provider = TracerProvider()

exporter = OTLPSpanExporter()
exporter.max_backoff_seconds = 5

processor = BatchSpanProcessor(exporter)
provider.add_span_processor(processor)
set_tracer_provider(provider)

tracer = get_tracer(__name__)

with tracer.start_as_current_span("test_span"):
    ...

[jakobdo]

I could also use this feature, it would be nice in our setup.