Enhance CI: add lint tests and automated test matrix across Ubuntu, macOS, and Windows

[kami922]

The existing CI runs only on windows-latest and only checks that the code compiles. No tests are run on any PR or push regressions go undetected until manual review.
Proposed jobs

• job 1: add linting tests

• job2: ubuntu test . here we will run build_tests_files.sh and run all tests for versions and binaries

• job3 and 4: not needed to run build_tests_files.sh here just check if they compile and run on windows and mac os on different jobs.

• job 5 build and release.

[kami922]

@stevemk14ebr let me know your thoughts .

[kami922]

i have a draft thats like quarter or semi done would like to hear your approach or suggestion as well.

[stevemk14ebr]

This sounds reasonable, I'd like some more details on the lint jobs done in job 1 . I'd want us to ensure lints are useful and standard, not a matter of opinion and noisy - ideally we rely on some default Go tooling.

For tests I think they could be in general extended. We definitely want the standard suite of binaries that the shell script generates to be tested against. This script produces stripped and non-stripped binaries for all 3 major OSs mac, lin, win. Our CI should test all these combinations. We can host this on a linux machine since GoReSym built for win should still parse lin, mac, win binaries just fine.

The existing release job I don't want modified significantly. I am happy with the way we zip releases and how the release build is triggered by a cut of a new github release.

[kami922]

@stevemk14ebr
for job 1 go fmt and and go vet should be enough they are official and contain zero opinionated-based rules.

for job 2 what you stated was the original plan of action I had in mind