chore(config): Add labels for new checks of Clang SA & Tidy

[whisperity]

The following checks were analysed on our usual set of ~20 test projects, these produced no crashes and most of them gave sensible results. Personally, I really enjoy the fact that bugprone-incorrect-enable-if is a thing!

• bugprone-empty-catch
• bugprone-incorrect-enable-if
• bugprone-non-zero-enum-to-bool-conversion
• bugprone-optional-value-conversion
• cppcoreguidelines-misleading-capture-default-by-value
• cppcoreguidelines-noexcept-destructor
• cppcoreguidelines-noexcept-move-operations
• cppcoreguidelines-noexcept-swap
• performance-noexcept-destructor
• performance-noexcept-swap
• readability-reference-to-constructed-temporary
• core.BitwiseShift
• unix.StdCLibraryFunctions

The following checks produced no reports on the test set, and as such, their evaluation was done by looking at the documentation and the tests. They also did not crash.

• bugprone-compare-pointer-to-member-virtual-function
• bugprone-multiple-new-in-one-expression
• bugprone-unique-ptr-array-mismatch
• cppcoreguidelines-no-suspend-with-lock
• misc-coroutine-hostile-raii
• modernize-use-constraints
• modernize-use-std-print
• readability-operators-representation

[vodorok]

Thanks for the classification, great work!
LGTM

[vodorok]

One question tho, there are some cppcheck checkers found by the coverage job.
Are you planning to review those too?

Checkers ADDED to upstream, without labels in CodeChecker:

• cppcheck-constParameterPointer
• cppcheck-constParameterReference
• cppcheck-constVariablePointer
• cppcheck-constVariableReference
• cppcheck-knownPointerToBool
• cppcheck-pointerOutOfBoundsCond

[whisperity]

@vodorok Eventually. We will need to do another round of the checker testing when the release is upon us...

I don't think there is an infrastructure in our internal CI to run CppCheck, unfortunately, so a large-scale evaluation is not really possible. 😖