[exporter/logging] Build exporter's logger from service's logger

[mx-psi]

Description:

Build the logger on the logging exporter's logger from the one on TelemetrySettings, so that the logger honors the configuration settings on telemetry::logs and the configuration options on CollectorSettings.LoggingOptions.

Depends on #5678

Link to tracking Issue: Fixes #5652

Documentation: Documented the feature gate.

[codecov]

Codecov Report

Merging #5677 (246c18b) into main (a7c047b) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #5677      +/-   ##
==========================================
+ Coverage   91.44%   91.53%   +0.09%     
==========================================
  Files         192      192              
  Lines       11416    11398      -18     
==========================================
- Hits        10439    10433       -6     
+ Misses        778      770       -8     
+ Partials      199      195       -4     

Impacted Files	Coverage Δ
exporter/loggingexporter/factory.go	100.00% <100.00%> (+22.22%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7c047b...246c18b. Read the comment docs.

[tigrannajaryan]

Arguably, the current behavior (not this PR's behavior) is desirable. When I am troubleshooting I often add a logging exporter and set it to debug level. I don't also want to enable debug level for everything else, it will be just too much noise in the logs.

If we feel there is inconsistency because logging exporter's debug level does not honour the main level setting, I suggest we do something else instead: the "loglevel" setting of the logging exporter should control whether the detailed output is generated, however that detailed output should be generated using info level, not debug level. So, essentially "loglevel" setting will control the behavior of the logging exporter, not the behavior of the logging exporter's logger. All output from logging exporter will happen at the info level. Once that change is made you can then pass the service's logger to the logging exporter to use.

[mx-psi]

@tigrannajaryan Right, this was the first alternative mentioned in #5677 (comment). It feels a bit weird to me, but I understand your point about wanting to filter the logs.

PTAL at #5678 which implements the suggested change. I will update this PR once that one is merged, marking as draft until then

[mx-psi]

Rewritten to not have breaking changes; depends on #5678

[mx-psi]

@tigrannajaryan this is ready for another look, I updated the PR description; this no longer introduces any breaking changes

[TylerHelmuth]

LGTM