[exporters/otlplog] Add support for OIDC authentication

[dpaasman00]

Problem Statement

This exporter is used by the collector for shipping internal telemetry. I'm looking for a way to configure this exporter to use OIDC authentication when sending the collector's internal telemetry.

Proposed Solution

Ideally there's new functionality to enable OIDC authentication.

Alternatives

The exact use case with the collector could be solved by the collector re-ingesting the telemetry it is emitting i.e. configuring this exporter to send to an OTLP receiver the collector is running. However I think it'd be better to avoid this.

Prior Art

The collector has an OIDC auth extension that can be used, but this is only available in pipelines the collector is running, not this exporter.

Additional Context

I've also opened an issue against the collector on this topic: open-telemetry/opentelemetry-collector#14241

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[axw]

Related spec issue: open-telemetry/opentelemetry-specification#1344

[dmathieu]

I think this would fall into the same case as support for OAuth authentication.

TLDR: You can already achieve this with a custom gRPC conn, or HTTP client.

We won't implement this without a specification as, as you can see, there are many authentication mechanisms and SDKs don't have the bandwidth to implement all of them.