Clang Checks

[dpaulat]

1. Changed files will undergo a format check. Visual Studio and Visual Studio Code should both format according to the same .clang-format set of rules that the job uses to check.
2. Changed lines will undergo a clang-tidy check. The rules are defined in a .clang-tidy file. I suspect I'll end up filtering out a couple additional checks, I attempted to take a first stab already. If the linter is incorrectly flagging something, a NOLINT comment can be applied (see clang-tidy docs).
   • The NOLINT should suppress ONLY the specific rule, and
   • include a note on why the lint check can be ignored or shouldn't be linted
   • The clang-tidy results will be added to the pull request as comments (up to 25). Anything over 25 will be available in a subsequent run, or as a json artifact from the job.
   • You can accept suggestions straight from the pull request too, even batch them from the file review tab.