Fix clang-tidy warnings for all C++ source files

[LinZhihao-723]

Request

Until 0c66d04, we have clang-tidy added to the linting tasks but disabled due to unresolved clang-tidy warnings across all C++ source files.
We should gradually resolve all these warnings.

Possible implementation

We shall send a serious of PRs to fix the warnings. Before all warnings are fixed, we should modify the lint task to only execute clang-tidy against fixed files (as discussed here). Eventually, we should have warnings resolved across all files, and we can set the lint task to run on all files (back to the config in 0c66d04)

New linting changes introduced to fix linting issues:

• bugprone-suspicious-stringview-data-usage: refactor: Fix clang-tidy warnings in Py_utils. #95
• Missing includes for third-party dependencies:
  • Having a directory wrapped_dependency_headers in parallel to clp_ffi_py
  • Each dependency has a wrapped header similar to Python.hpp introduced in feat: Add Python class KeyValuePairLogEvent as a wrapper of clp::ffi::KeyValuePairLogEvent. #81:
    • Exporting the super header
    • Exporting any internal headers used by clp_ffi_py when CLP_FFI_PY_ENABLE_LINTING is defined
• Disable cppcoreguidelines-pro-type-vararg: refactor: Fix clang-tidy warnings in utils. #101
• Add clang-tidy command line option to bypass problematic lines in msgpack source code as a temporary solution for Clang-tidy raises a warning in msgpack's source code. #109: refactor: Fix clang-tidy warnings in PyKeyValuePairLogEvent. #108.

[LinZhihao-723]

clang-tidy enabled in #99