added scheduled Clang Static Analyzer run

[firewave]

• added CMake target run-clang-tidy-csa to run Clang Static Analyzer
• added CMake option ENABLE_CSA_ALPHA to enable the alpha checkers

[firewave]

As it wrecks havoc on the performance (I did not remember it being so bad) we should limit this to the CI so it won't kill the usability IDEs which support clang-tidy.
of

[ 59/240][305.7s] clang-tidy-19 -p=/home/runner/work/cppcheck/cppcheck/cmake.output -quiet /home/runner/work/cppcheck/cppcheck/test/testother.cpp

OTOH it is a bit of relieve to see that other dataflow implementations also seem to struggle with some "heavy" patterns.

[firewave]

OTOH it is a bit of relieve to see that other dataflow implementations also seem to struggle with some "heavy" patterns.

It appears they are also slow with big if-else chains.

[firewave]

Some of the times are misleading because some of the files are analyzed more than once because of llvm/llvm-project#73357 (comment).

[firewave]

I filed llvm/llvm-project#132001 about the clang-analyzer-optin.cplusplus.UninitializedObject false positives with unnamed fields used for explicit padding.

[firewave]

It would be great to have a badge for this run on the main page but I have no idea how to differentiate the scheduled run from a regular one.