test: run linux package tests nightly against latest contrib main

[mowies]

This PR enables nightly testing of the otelcol-contrib linux packages based on the latest main branch version of otelcol-contrib built in https://github.com/open-telemetry/opentelemetry-collector-contrib.
This change was made possible by splitting the otelcol-contrib gorelease config into 2 separate files, one for building and one for packaging/archives/docker images/etc.
(The split goreleaser build is a goreleaser pro feature)

Using the split building approach was the only viable option to achieve this. I did lots of research on this, it was talked about in the Collector SIG meeting and I also asked the GoReleaser folks for their help.

Consequences of this change:

• better testing
• slightly less maintainability of the goreleaser files and generator code for otelcol-contrib since they have special handling now

Fixes #659

[mowies]

@mx-psi i fixed all your remarks, pls re-review when you find some time :)

[mx-psi]

I have re-run the CI but it keeps failing, can you take a look? Do you think it is related to the 2.4.6 update?

[mowies]

yes i think it's related somehow. there were some changes to folder naming that i need to adapt to I believe. This will also be needed on the renovate PR

[mx-psi]

Oki, if you'd rather revert the 2.4.6 update I'm also okay with that, just ping me on a revert PR :)

[mowies]

Maybe i will wait until we merge the updated goreleaser version in main. That will require some manual changes as well I think. Maybe you could retrigger CI there and then let's see what happens.
PR link: #752

[mowies]

@mx-psi i believe i'm done with all the review comments and refactoring etc.
would appreciate a re-review when you have time :)

[mx-psi]

LGTM! I am bit scared about accidentally breaking the release pipeline with this change. There's a couple things that can be done here: a test release run on your fork and waiting until right after the next release to maximize the time we test this. What do you think?

[mowies]

you mean merging this only after the next release?
doing a release on my fork sounds good

[mx-psi]

you mean merging this only after the next release?

Yep

doing a release on my fork sounds good

Alright, if you find the time, I suppose it will fail when pushing to the Docker registry but if it passes until then that's a good test for me

[mowies]

Sounds good, I'll do the test release next week

[mowies]

i tried to do a test release but it's hard to do with so many otel specific things. Even after removing the container registry login steps, goreleaser needs the pro key for example. But here are the test runs that ran until the requirement for the goreleaser-pro key:

Builder
Core
Contrib
k8s
OTLP

In any case, this PR doesn't touch any of the release pipelines anyways.

[mowies]

@mx-psi so now it was still merged before the collector release 😅

[mx-psi]

@mx-psi so now it was still merged before the collector release 😅

Sorry, should have said something here before merging: I spoke with Antoine (this week's release manager) about this and he was fine to merge this before the release 😄

[mowies]

ah okok 😄