Consider removing cmd/otecontribcol and cmd/otetestbedcol modules

[dmitryax]

Go code in the cmd/otecontribcol and cmd/otetestbedcol modules is auto-generated using the collector builder. cmd/otecontribcol also has additional lifecycle tests for all the components that do not necessarily belong to that module.

The go modules depend on all the other modules in the contrib repo. This makes the linter take up to 20 minutes just to build AST. The linter job often times out.

Do we really need to keep the generated code? Instead, we can generate the code whenever we need to build the otecontribcol or otetestbedcol artifacts. The lifecycle tests can be moved to each component by autogenerating them with the mdatagen tool.

Action items (assuming the suggestion is accepted):

• Move the lifecycle tests with to each component module #27849
• Remove generated code from cmd/otecontribcol or cmd/otetestbedcol #27850

[codeboten]

I would be ok with removing it, so long as the makefile targets continue to work, that's fine w/ me. We should consider doing the same in core

[dmitryax]

The suggestion was accepted after discussing it in the Collector SIG meeting

[jpkrohling]

I'm in favor of removing it. I'd love to get @bogdandrutu's opinion on this, as I remember him being quite vocal about having that versioned.

[atoulme]

I would like to work on this. I will start with moving the tests out per the list.