CodeChecker finds all old issues again when renaming a file

[jimis]

• File had a bunch of unreviewed issues but they were being ignored
• File gets renamed in a git commit
• New run of CodeChecker analyze presents all the old issues as new. The report hash appears to be different, the issues are shown on the UI like they have no history.

[csordasmarton]

@jimis The problem at here is that the report hash contains the file name which is described at here: https://github.com/Ericsson/codechecker/blob/master/docs/analyzer/report_identification.md. I don't know what would be the best choice to solve this problem. Maybe we can create a new context free hash method (context-free-v3) where we skip the file name from the report hash so the hash will contain only the following information:

• checker name (e.g.: bugprone-infinite-loop, core.DivideZero etc.).
• content of the line where the bug is if it can be read up. All the whitespaces from the source content are removed.
• range column numbers where the bug is.

Is it sounds good to you or do you have any other recommended solution to this problem?