Workflow for code analysis

[simonsan]

Early stage, aims for:

• giving feedback if bugs are found
• optimize that patch-formatting
• publish fixes (patches) for found errors based on settings in .clang-tidy
• publish fixes (patches) based on settings in .clang-format
• use it just on the recent pushed commit, not over all the code base
  • include switch, we want to check the code base and fix stuff from time to time
• LINK_WHAT_YOU_USE
• make use of clazy (Qt related compiler warnings)
• cpp-lint (not needed => Clang-Format)

Buildsystem-Flags
Q: Does it make sense to create a diagnose module under buildsystem for make diagnose or would it be enough to document the following switches and create some CMake file around it or so for exporting fixes (incl. Clang-Tidy that is already existing)

• Include-what-you-use
• cppcheck
• clang-tidy

Future:

• use result of Add clang-tidy to buildsystem checks #1157 and integrate it into the workflow

ref.: #1196

[simonsan]

(Outdated)