debug_tools path replacement can be incorrect

[balazske]

Describe the bug prepare_analyzer_cmd.py may create wrong compile commands in compilation_database_DEBUG.json file. Every include path starting with '/' in the commands is replaced with the absolute path. An option like -I./dir/file.h is changed to -I.<absolute include path>/dir/file.h which is not correct in this case. It should be correct if relative paths are not changed at all, because the build directory layout is similar as the original.

CodeChecker version

[INFO 2022-12-22 10:07] - CodeChecker analyzer version:
---------------------------------------------------------------
Kind                 | Version                                 
---------------------------------------------------------------
Base package version | 6.21.0-rc                               
Package build date   | 2022-11-29T16:22                        
Git commit ID (hash) | 10e43bc4200adc1949590185ff48f3c842516515
Git tag information  | 6.21                                    
---------------------------------------------------------------
[WARNING 2022-12-22 10:07] - This version is only a release candidate! If you encounter any problems, please submit a bug report!

To Reproduce Steps to reproduce the behaviour: Use prepare_all_cmd_for_ctu.py with a failure report and compile_commands.json that contains include path names with relative directories. The output may show errors if the compilation or AST generation was not successful because not found include files. Probably analysis with analyzer_command_DEBUG runs correctly but the analysis results are different, and the crash to reproduce with the scripts does not show up.

Expected behaviour Relative include paths should not be replaced in the compile commands.