autoexport: Add support for console exporters

[codeboten]

This adds support for the standard output exporter for traces and metrics. To remain consistent with other implementations, i used the key console as the identifier for the exporter. This change is related to the specification pull request open-telemetry/opentelemetry-specification#3742

[codecov]

Codecov Report

Merging #4486 (00570c2) into main (19346a7) will decrease coverage by 0.1%.
The diff coverage is 66.6%.

@@           Coverage Diff           @@
##            main   #4486     +/-   ##
=======================================
- Coverage   80.9%   80.9%   -0.1%     
=======================================
  Files        150     150             
  Lines      10304   10313      +9     
=======================================
+ Hits        8339    8345      +6     
- Misses      1825    1827      +2     
- Partials     140     141      +1     

Files	Coverage Δ
exporters/autoexport/spans.go	92.0% <100.0%> (+1.0%)	⬆️
exporters/autoexport/metrics.go	79.5% <50.0%> (-2.4%)	⬇️

[pellared]

open-telemetry/opentelemetry-specification#3742: it would be good to make sure there is an agreement on the "name" before merging 😉

[codeboten]

Thanks for reviewing @pellared, I agree that having a consistent name would be good :) This is at least consistent w/ 3 (python, js, ruby) implementations. Java uses the term logging https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#logging-exporter which I worry is causing the same confusion as the logging exporter did in the Collector before it was renamed to debug

[pellared]

This is at least consistent w/ 3 (python, js, ruby) implementations.

I suggest calling it out in open-telemetry/opentelemetry-specification#3742