Migrate GitHub build action to use GoReleaser

[frenck]

This PR migrates the GitHub Action for building the OS Agent to use GoReleaser.

• Add GoReleaser
• Set up for our supported architectures
• Added Debian packages creation, including handling of services and dbus configs on install/removal of the package
• Publish build artifacts to GitHub

Possible future improvements (needs more testing):

• Handle CodeNotary better. Right now, it signs all resulting binaries, similar to what is done now. Ideally, we sign all resulting assets as well, which could be done from goreleaser.
• Publish as APT repo. E.g., using CloudSmith, Fury.io or self hosted using aptly tooling or something.

I left the latter 2 out of scope for this PR, mainly to get something going.

Testing: I've been playing with the result and development on a fork
https://github.com/frenck/os-agent/releases/tag/1.8.0

[ludeeus]

Suggested change

	`1.0.0` is used as an example here, replace that with the version of the file you downloaded.

[ludeeus]

Not needed if name_template is used

[frenck]

We should use the name template as is if we have the ambition to publish it to an apt repo. In that case, you want the files to be distinctive in order to work with multiple versions.

[ludeeus]

Suggested change

	wrap_in_directory: true
	files:
	wrap_in_directory: true
	name_template: '{{ .ProjectName }}_{{ .Os }}_{{ .Arch }}{{ end }}'
	files:

If we do not add the version to the file, instructions become simpler, and you can have a direct link to the latest asset.

[frenck]

I don't agree with that, as the goal should be publishing it in an apt repository.
We also can't link directly, as there are multiple architectures available.

PS: The suggested name template would probably fail, as we have multiple of the same architecture (different arm versions, but still a single arm arch)

[frenck]

For example:

[pvizeli]

Looks good to me