Stricter builds

[Mher594]

To ensure high code quality we can use

1. Stricter compiler warnings.
2. Fix issues with clang-tidy checks in GitHub actions

For stricter compiler warning we can use something like

target_compile_options(main PRIVATE
  $<$<CXX_COMPILER_ID:MSVC>:/W4 /WX>
  $<$<NOT:$<CXX_COMPILER_ID:MSVC>>:-Wall -Wextra -Wpedantic>
)

As for clang-tidy issue we need to make sure that it runs during build action (at least for Linux builds). Currently in our codebase we have misc-const-correctness warnings but the build is successful for #40 PR