Valgrind independent of paths

Notice that there were a few commits on top of ccf662c, so ive recreated the patch on top of those. So it will be easy to merge later after review.

SONARPLUGINS-2981: The idea here is, that there is no valid solution to cases where for example user changes paths, the only way the violations will be found is if we use the AST to find the location of the functions in the source code. Thats the idea behind this pull request, this adds a bit of overhead to the analysis however it fixes the problems.

Further improvements in the future could be create lookup tables only once when source is imported and make them available to sensors that they later reuse.

The lookup table will be created only if there are reports defined, so might be a good idea to extend this the xunit parser.

Please review, thanks