feat(ci): add script to validate each commit in PR

[inosmeet]

Purpose of PR?:
Implement feature that ensures that each commit of PR is separately compiles.
Closes: #616

If the changes in this PR are manually verified, list down the scenarios covered::
Manually tested in fork, with both appropriate commits that should and does compile as well as invalid commits that should and does fail.

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[inosmeet]

cc @Ankurk99 @achrefbensaad

[inosmeet]

Hey @daemon1024!
Can I get a review?
Thanks!

[Ankurk99]

Hey, thanks for the PR. I have a few suggestions.
Also, did you test these changes anywhere?

[Ankurk99]

Consider using go-version-file: KubeArmor/go.mod for defining go version

[Ankurk99]

I would also recommend showing the error in the logs

[inosmeet]

GitHub Actions captures all logs from make build, do we need to add manual logs?
for example, here's the log from GH action when i was testing manually:

Error: ./main.go:40:68: syntax error: unexpected newline in argument list; possibly missing comma or )
Error: ./main.go:41:4: syntax error: unexpected return at end of statement
make: *** [Makefile:26: build] Error 1
❌ Commit e52b12d577936188e5b7aea2c9ddb30fb6b60b17 failed to compile!
=========================================
Error: Process completed with exit code 1.

[inosmeet]

did you test these changes anywhere?

Thanks for reviewing!
Yeah, I manually tested these in my fork.
I followed these steps:

1. Made a PR to my fork which included a couple of commits that were appropriate (which passed).
2. On top of the appropriate commits, I deliberately made a few commits that had some faults (which failed as the should).

I'm not sure whether there should be a test for this?