Support OTEL_EXPORTER_OTLP_LOGS_INSECURE and OTEL_EXPORTER_OTLP_INSECURE environments in grpc exporter

[amanakin]

Closes #5719

In this commit I add OTEL_EXPORTER_OTLP_LOGS_INSECURE and OTEL_EXPORTER_OTLP_INSECURE env options to otlploggrpc.Exporter.

Now insecure option is fetched from env endpoint value (OTEL_EXPORTER_OTLP_LOGS_ENDPOINT/OTEL_EXPORTER_OTLP_ENDPOINT).
According to spec:

Insecure: Whether to enable client transport security for the exporter’s gRPC connection. This option only applies to OTLP/gRPC when an endpoint is provided without the http or https scheme - OTLP/HTTP always uses the scheme provided for the endpoint.

So with current behavior we have several problems:

• If default endpoint is used, we can't use insecure connection (with setting OTEL_EXPORTER_OTLP_INSECURE).
• If endpoint provided with option without scheme (e.g. WithEndpoint) we can't use insecure connection with env settings.
• If endpoint provided with env variable without scheme (e.g. //env.endpoint:8080/) we can't use insecure connection.

This commit fixes this.

The same problem with otlploghttp.Exporter, and probably it should be fixed there too.
I'm open to suggestions on how to fix the current behavior in a more elegant way.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.6%. Comparing base (fb7cc02) to head (1703736).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #5739   +/-   ##
=====================================
  Coverage   84.5%   84.6%           
=====================================
  Files        272     272           
  Lines      22759   22778   +19     
=====================================
+ Hits       19253   19271   +18     
  Misses      3166    3166           
- Partials     340     341    +1     

see 2 files with indirect coverage changes

[amanakin]

Can anyone take a look? 👉👈