separate flags if customer report itself is valid, and customer report matches manufacturer report (for UI)

refactoring of XML validation: consider schema version number read from document, use single class for validating all vecto-related xml files

change method to obtain vecto version number: instead of reading out from dll, use (same) t4 macro to statically compile the version number as static property; slightly adapt build process to compile t4 macros

refactoring: connect job directly to report viewmodels (without verifyresults as mediator), more validation tests,

add certification number and digest values output and check to verify results view, splitting up into multiple files

fix: check if a job-file is loaded before computing the hash; update hash when new job-file is loaded

fix: updating canonicalization method works; corrected comparison of job hash for report integrity checks

refacotring modelviews to use base class from report validation, more expressive icons for validating input

refactoring: use common model for validating job and results, full job-file validation when validating results