VAT findings API validation

The finding result sets from the VAT SQL query, currently being used to generate the pipeline's whitelist, and the VAT API response, are not always the same. Our goal is to switch the pipeline over to using the newer API response as this takes advantage of the VAT's logic for inheritance and finding de-duplication. The best way to do this validation is to use the output of the Trigger project to find all of the pipelines that failed the finding compare job within the CHT pipeline. We need to validate if the differences in data makes sense, or if we need to ask the VAT team to update their API.