[Traces + Logs] Clean up repo exporters to use new DI patterns

[CodeBlanch]

Changes

Updates the trace & logging exporters to use the new DI API surface.

OtlpLogExporter got a couple features with this upgrade:

• Now obtains its options instance through IOptions so it can be bound to IConfiguration
• Now calls the TryEnableIHttpClientFactoryIntegration helper so it should also be able to use HttpClientFactory integration

TODOs

• Appropriate CHANGELOG.md updated for non-trivial changes

[CodeBlanch]

@alanwest You want me to spin up an issue for this?

[codecov]

Codecov Report

Merging #3640 (f6c5980) into main (5208ec0) will increase coverage by 0.00%.
The diff coverage is 94.73%.

❗ Current head f6c5980 differs from pull request most recent head c3e98d3. Consider uploading reports for the commit c3e98d3 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3640   +/-   ##
=======================================
  Coverage   87.35%   87.35%           
=======================================
  Files         282      282           
  Lines       10132    10142   +10     
=======================================
+ Hits         8851     8860    +9     
- Misses       1281     1282    +1     

Impacted Files	Coverage Δ
...ryProtocol.Logs/OtlpLogExporterHelperExtensions.cs	90.47% <83.33%> (-1.84%)	⬇️
....Exporter.Jaeger/JaegerExporterHelperExtensions.cs	97.67% <100.00%> (+2.32%)	⬆️
...metryProtocol/OtlpTraceExporterHelperExtensions.cs	90.90% <100.00%> (+5.19%)	⬆️
....Exporter.Zipkin/ZipkinExporterHelperExtensions.cs	97.61% <100.00%> (+2.49%)	⬆️
...Propagators/OpenTelemetryPropagatorsEventSource.cs	87.50% <0.00%> (-12.50%)	⬇️
...emetry.Api/Internal/OpenTelemetryApiEventSource.cs	73.52% <0.00%> (-5.89%)	⬇️
src/OpenTelemetry/Logs/OpenTelemetryLogger.cs	86.66% <0.00%> (-2.23%)	⬇️
...metryProtocol/Implementation/ActivityExtensions.cs	95.05% <0.00%> (-1.10%)	⬇️
...Telemetry/Internal/SelfDiagnosticsEventListener.cs	97.65% <0.00%> (+0.78%)	⬆️
... and 2 more

[TimothyMothra]

Will the same change come to metrics?

InMemoryExporterMetricsExtensions also uses the IDeferredMeterProviderBuilder pattern.
I wrote tests for this in the OpenTelemetry.Extensions.Hosting.Tests project: InMemoryExporterMetricsExtensionsTests.

[CodeBlanch]

@TimothyMothra

Will the same change come to metrics?

Totally! My goal is for all three signals to have the same (~) API for build-up. I'll start on metrics after a couple of these clean-up PRs for traces + logs.