@jack-berg is this still "experimental"?  Should we consider making it official at this point?

Originally posted by @tylerbenson in #3791 (comment)

@tylerbenson asks if we can stabilize the OTEL_EXPERIMENTAL_EXPORTER_OTLP_RETRY_ENABLED autoconfigure environment variable.

It's existed for quite a while, first added in Oct 2021, and hasn't changed at all since.

However, the environment variable doesn't exist in the spec, and the spec is still very sparse on details of how retry should work: open-telemetry/opentelemetry-specification#1742

Back in 2021 I was hopeful that the spec would clear up OTLP retry requirements such that all the implementations could standardize. However, since then:

• OTLP stabilized without retry details
• In the absence of specifics, various retry implementations have made their own assumptions on the set of configurable parameters and the behavior. I.e. the collector's set of parameters and defaults are different than java's, and dotnet's, etc.
• A moratorium was added preventing addition of new environment variables until file configuration is hashed out
• Java stabilized programatic configuration of retry. This means we're locked into supporting the set of parameters and probably the exponential backoff behavior.

I'd like to propose that we move forward with a stable java specific environment variable which simply toggles retry on / off. Something like:

OTEL_JAVA_EXPORTER_OTLP_RETRY_ENABLED