[exporterhelper] Propose refactor of internal/queuebatch package

[jackgopack4]

Component(s)

exporter/exporterhelper

Describe the issue you're reporting

It seems that internal/queuebatch package is growing rather large and interdependent.

Given comments on #12934 (#12934 (comment)), it could be worthwhile to separate a queue/batcher interface and have separate package or packages for the various implementations (i.e. async queue, memory queue, persistent queue as well as default batcher/disabled batcher).

I propose leaving queuebatch as an interface-driven package potentially renaming as something like queuebatchinterface, and creating individual "batcher" and "queue" packages for the implementations. This would be done in multiple steps.

Alternatively, there could be a "queue" and a "batch" internal package that defines the interface and common code, and sub-packages under those package for each queue and batcher implementation.

Would be happy to discuss concerns/advice with regards to this proposal.

[github-actions]

Pinging code owners:

• exporter/exporterhelper: @bogdandrutu @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jackgopack4]

so it seems like the dependencies are pretty tight, seeing if I can use dependency inversion with queuebatch and the various queue/batcher implementations