Add ability to use aggregate logger in pipeline

[pkositsyn]

Is your feature request related to a problem? Please describe.
Currently we cannot globally limit number of logs, produced by the pipelines. The common mistake among the whole repository is that every request can result in a log in some consumer, which overrides logging pipelines. Yesterday I got the situation, such that collector started producing 150k logs/min because of exporter failure (which was external error actually).

Describe the solution you'd like
I think the best way to avoid such situations is adding config options for general logger, passed into every consumer.
This is already done in logging exporter and I like this as a way to limit logs

opentelemetry-collector/exporter/loggingexporter/factory.go

Lines 90 to 111 in 2c8915a

	func createLogger(cfg *Config) (*zap.Logger, error) {
	var level zapcore.Level
	err := (&level).UnmarshalText([]byte(cfg.LogLevel))
	if err != nil {
	return nil, err
	}
	// We take development config as the base since it matches the purpose
	// of logging exporter being used for debugging reasons (so e.g. console encoder)
	conf := zap.NewDevelopmentConfig()
	conf.Level = zap.NewAtomicLevelAt(level)
	conf.Sampling = &zap.SamplingConfig{
	Initial: cfg.SamplingInitial,
	Thereafter: cfg.SamplingThereafter,
	}
	logginglogger, err := conf.Build()
	if err != nil {
	return nil, err
	}
	return logginglogger, nil
	}

[andrewhsu]

closing as duplicate because this issue is taken care of in #2102