OkHttpHttpSender should support COMPATIBLE_TLS connectionSpec

[jameyg42]

Is your feature request related to a problem? Please describe.
The OkHttp based exporter can only export to https:// endpoints that meet the requirements of the OkHttp MODERN_TLS ConnectionSpec.

Describe the solution you'd like
the OkHttpHttpSender should support the COMPATIBLE_TLS ConnectionSpec (possibly via a config switch)

Describe alternatives you've considered
A custom ExporterSender, but hits on #6718

Additional context
Certain WebSphere 8.x systems (java 1.8) running on AIX platforms (for example) cannot export to https:// endpoints. The J9 1.8 JVMs cannot satisfy the requirements of OkHttp MODERN_TLS and there is no available otel-collector for AIX to handle a http://localhost type setup.

[jack-berg]

there is no available otel-collector for AIX to handle a http://localhost/ type setup.

I don't understand. You can definitely run the collector in a way that its accessible on http.

meet the requirements of the OkHttp MODERN_TLS ConnectionSpec.

I'm not familiar with this. Can you link to some documentation? Alternatively, maybe open a draft PR sketching out the rough idea for what would be required in OkHttpHttpSender.

[jameyg42]

sorry for the confusion - in my example, i just meant that the otel-collector itself (or really anything golang) doesn't currently run on AIX, so the typical apm-agent --> http://localhost:4318 --> final-destination setup can't be done on that platform
open-telemetry/opentelemetry-collector-contrib#19195

company rules prevent me from submitting a PR, but relaxing OkHttp TLS (which is likely needed to support many Java 1.7 distro's too) would be something along the line of adding

OkHttpClient.Builder      .......
   .connectionSpecs(singletonList(okhttp3.ConnectionSpec.COMPATIBLE_TLS))

to OkHttpHttpSender (and maybe OkHttpGrpcSender too)
https://square.github.io/okhttp/security/tls_configuration_history/