use builddir consistently and verify usage of cached results in selfcheck / improved --debug-analyzerinfo output

[firewave]

No description provided.

[firewave]

Requires #8198 and #8159 to be merged first.

[firewave]

discarding cached result from 'b1/main.a1' for 'cli/main.cpp' - hash mismatch (16146913026568202460 / 18076949867239869788)
discarding cached result from 'b1/main.a1' for 'gui/main.cpp' - hash mismatch (18076949867239869788 / 16146913026568202460)

The problem is that we perform individual analysis(eses) on the same builddir leading to conflicts when a file with the same name exists in a different location.

I am not sure this can be resolved as the files.txt is written unconditionally essentially discarding.

A valid use case would be the usage of a cache in conjunction with an IDE integration which would only invoke the analysis for a single file. In that case though we could generate the files.txt for the whole project/inputs regardless of the selected subset. But that would only work with a fixed project configuration but not in the case of this PR when you extract configurations.

It could be achieved though by not writing the file unconditionally but use it as an index for lookups and append new entries. This would leave outdated and/or removed files behind but that is already an issue now (needs a separate ticket).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud