feat: Create Updater artifact

[BinaryFissionGames]

Proposed Change

• Create a new "updater" binary
• Add make target for updater
• Modify other build targets to include building the updater
• Add to MSI build
  • It's automatically added to other builds (linux packages, archives)
• Implement version print flag for updater

Tested on linux & windows, checked the tar archive for darwin to make sure that the updater exists.

Tested manual build for Win MSI.

Checklist

• Changes are tested
• CI has passed

[cpheps]

Curious if there are any concerns with this not being in its own package and being its own go.mod? It's currently sharing a mod file with the collector. Do we expect a lot of overlap between the two that it's worth sharing a module?

[BinaryFissionGames]

That's something that I haven't considered; It might make sense to split into a separate module. I'll try it out and see what it's like.

[cpheps]

That's something that I haven't considered; It might make sense to split into a separate module. I'll try it out and see what it's like.

@BinaryFissionGames you might hit issues with goreleaser. I thought you need the pay version to do multiple binaries in submodules. I think it's the monorepo feature set.

[BinaryFissionGames]

Yeah, looks like go does not play nice with the updater binary being in its own module:

cd ./updater/; go build -ldflags "-s -w -X github.com/observiq/observiq-otel-collector/internal/version.version=v1.2.0" -o ./dist/updater_darwin_amd64 ./cmd/updater
main module (github.com/observiq/observiq-otel-collector) does not contain package github.com/observiq/observiq-otel-collector/updater/cmd/updater

Might makes sense to make a new module for all the underlying logic, but it doesn't seem to work well for the main.go

[BinaryFissionGames]

Spoke too quick, it was a local environment issue.

I broke it into a separate module, seems to work just fine, so we should switch to that. It should be almost entirely separate from the collector code, so it makes sense.

[armstrmi]

@BinaryFissionGames @cpheps Could you guys give a generic overview of a concern for not having the updater in its own package and having a go.mod file instead, would there be confusion between the base level go.mod file? and Why @BinaryFissionGames was it originally configured that way?

[cpheps]

@armstrmi Because the updater is meant to be its own binary having it in its own module we can better separate it from the collector binary. By having its own module to we can separate the dependencies needed for the updater from the collector dependencies. Since the collector by, nature of what it is, has a large number of dependencies this could over complicate managing dependencies for two separates binaries.

If we come to find there there is some shared code between the two binaries we could break that shared code out into a third module that is shared between the two.