[JENKINS-17363] Ludicrously slow load time [with lazyloading]
[JENKINS-19437] Implement load on demand functionality in Cppcheck

- All details from Cppcheck report is stored to build.xml which is wrong. The file quickly grows with many findings and causes performance and memory issues.
- Storing of the details to external file cppcheck_details.xml and their lazy loading implemented to fix the issue. File build.xml now contains only small statitistics neccessary for trend graph and build summary.
- There is no need to store CppcheckReport during the build at all, its content is fully dupplicated in CppcheckSourceContainer. CppcheckStatistics has nearly identical interface so it can be used instead of CppcheckReport most of time.
- Incorrect uses of @SuppressWarnings("unused") removed to solve compiler warnings.
- Cppcheck tool version is stored to build.xml together with CppcheckStatistics now. This fixes a bug in the details page, the information was expected in CppcheckReport but its field is transient so the information was never stored/loaded and displayed.
- Content of tabview/main.jelly moved dirrectly to CppcheckResult/index.jelly, include removed. This was probably only a historical location.
- New developer added to pom.xml.
- Several TODOs unrelated to this commit added to the code, they will be fixed in future.