Fix multiple exporters panic

[sumo-drosiek]

Description:
Fixing a bug

While using more than one exporter the panic runtime exception occured,
because the array allocated for exporters was as twice as big as it should

Link to tracking Issue: N/A

Testing:

Using more than one exporter results with panic runtime error:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x510ca95]

goroutine 108 [running]:
go.opentelemetry.io/collector/processor.LogFanOutConnector.ConsumeLogs(0xc0002c0d40, 0x4, 0x4, 0x88ab900, 0xc0002c10c0, 0xc00082a000, 0xc000c19880, 0x2)
        .../processor/fanoutconnector.go:171 +0xb5

Documentation: N/A

Signed-off-by: Dominik Rosiek drosiek@sumologic.com

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Dominik Rosiek (b4e2548)

[codecov]

Codecov Report

Merging #1563 into master will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #1563   +/-   ##
=======================================
  Coverage   91.47%   91.47%           
=======================================
  Files         250      250           
  Lines       17315    17315           
=======================================
  Hits        15839    15839           
  Misses       1062     1062           
  Partials      414      414           

Impacted Files	Coverage Δ
service/builder/pipelines_builder.go	82.78% <0.00%> (ø)
translator/internaldata/resource_to_oc.go	81.25% <0.00%> (ø)

---

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 8e5c606...b4e2548. Read the comment docs.