Add CI github actions workflow to verify builds on pull_request

[tairov]

This CI workflow provides a system that ensures every change made to the master branch, specifically to Makefiles, *.h, or C source files, doesn't break the build process, improving the reliability and stability of the project.

It'd be nice to have basic build validation in order to avoid issues on different platforms like this one : #80

Builds validation platforms:
Linux : ✅
MacOS : ✅
Windows : ✅

[tairov]

CI pipeline looks good : https://github.com/tairov/llama2.c/actions/runs/5662603534

[karpathy]

Actually I like this, but few things:

• is windows somehow harder to include?
• can we make naming inside Makefile consistent?
• can we make the actions specific to this repo? e.g. there are no header files so there is no need to include anything .h

[karpathy]

(By consistent I mean no underscores in target names, e.g. just make it clangomp or something?)

[tairov]

I agree regarding naming consistency -- Fixed.
Windows builds turned out to be a bit harder to verify on my Mac M1, I'm looking for a solution to reproduce environment locally.
I thought, maybe someone experienced with Windows msbuild can give a hand, if not, I'll sort this out till tomorrow I hope

[tairov]

@karpathy added windows platform build job (pipeline : https://github.com/tairov/llama2.c/actions/runs/5663670418 )

Erorrs with Windows builds ignored at the moment:

continue-on-error: true

Seems that compilations on Windows are not working via CL.exe at least , #91

Also removed irrelevant *.h targets from trigger paths

[tairov]

Adapted build.yml to latest changes in master ( tuneable compiler config )

[tairov]

Fixed builds for windows . Now CI workflow uses build_msvc.bat

[karpathy]

@tairov please let me know when you think this could be good to merge. CI would be very nice!

[tairov]

Code rebased to catch up with upstream/master

@karpathy it's ready to be merged.

On my fork I'm using this to check builds for multiple platforms instantly - linux, macos, window (x86, 64, arm) very convenient.
Also I've adapted windows steps to use .\build_msvc.bat already.

Here is example how action execution will look like once a PR created in the repo that propose changes in any following files *.c, *.h, Makefile

[karpathy]

Exciting, thank you!