Adding all components for testbed

[swamisriman]

Description:
Adding all components from otelcontribcol to oteltestbedcol.

Link to tracking Issue:
Resolves #33193

Testing:
When using the following processors in tests/resource_processor_test.go/TestMetricResourceProcessor(...), the test passes.
See the linked issue for context.

processors := map[string]string{
				"resource":  test.resourceProcessorConfig,
				"transform": "\n  transform:\n",
			}

[rogercoll]

Do we want to add all the components to the binary even if they are not used in the tests/testbed package? What would be the benefit?

[rogercoll]

Should we update the contributing guides accordingly? New components should be added to the binary too: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components

[swamisriman]

What would be the benefit?

@rogercoll
I feel that it would keep the experience consistent across otelcontribcol and oteltestbedcol.

Users of the OpenTelemetry Collector are also encouraged to build their own custom distributions with the OpenTelemetry Collector Builder, using the components they need from the core repository, the contrib repository, and possibly third-party or internal repositories.

Taken from repo README.
I think the same principle applies here.

Also, I don't think we are publishing any pre-built testbed binaries (are we??)

[rogercoll]

Another approach would be to remove the testbed binary in favor of the otelcolcontrib one, related PR: #34849

[swamisriman]

oh...yeah
that would be even neater - to use the same contrib binary for tests too.

[swamisriman]

So, what do you say guys?
Shall we skip this in favour of #34849 ?
Or will this be an interim solution?

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.