Make the build consistent across archs for Go to correctly report the package path inside the binary

[macedogm]

The amd64 build process is passing directly the ./main.go file for the build. According to golang/go#36793, this results in Go not properly identifying the package and module path and then marking the compiled binary as command-line-arguments. This doesn't happen with the arm64 build.

The resulting effect is the following:

wharfie-amd64

go version -m wharfie-amd64 | head -n 3
wharfie-amd64: go1.22.7
	path	command-line-arguments
	dep	github.com/NYTimes/gziphandler	v1.1.1	h1:ZUDjpQae29j0ryrS0u/B8HZfJBtBQHjqw2rQ2cqUQ3I=

wharfie-arm64

go version -m wharfie-arm64 | head -n 3
wharfie-arm64: go1.22.7
	path	github.com/rancher/wharfie
	mod	github.com/rancher/wharfie	(devel)

The wharfie-amd64 binary lacks the mod github.com/rancher/wharfie identification. Although this is a minor thing and that doesn't affect the binary itself, it actually blocks security scanners, for example Trivy, from correctly matching the binary (and its path/module origin) with a VEX entry, as an example, see this entry.

This was identified internally when a false-positive vulnerability that was supposed to be suppressed was still being reported in the scanning reports.

[macedogm]

PTAL @brandond / @dereknola

After this is merged, if approved, can we cut a new patch version, please?

[macedogm]

@knqyf263 pinging you in case of curiosity.

[knqyf263]

Great!