Remove generated code from `cmd/otecontribcol` or `cmd/otetestbedcol`

[dmitryax]

Don't need to keep the generated code. We can keep the builder yaml manifests only, and generate the code when it's needed.

1. Find a better place for the collector builder yaml manifests
2. Update all the CI steps and make targets to generate the code before building artifacts
3. Remove the cmd/otecontribcol or cmd/otetestbedcol modules

[github-actions[bot]]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[codeboten]

come on github-actions, do you not see all the PRs opened on this issue? 😄

[github-actions[bot]]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[mowies]

I started working on this, draft PR is open but still in progress.

@dmitryax what about the test files found in cmd/otelcontribcol? Also, I will maybe have to keep the dockerfiles to build images of the collector that are needed in the pipeline.

[mowies]

@dmitryax any updates on this?

[mowies]

maybe somebody else from @open-telemetry/collector-contrib-maintainers ?

[mowies]

or @atoulme since you worked in removing things here as well?