{{discoverReferenceBuild }}will not update to the latest completed build after being called for the first time.

Scenario:

1. Build A is completed
2. Build B starts
3. Build C starts and calls discoverReferenceJob -> points to A
4. Build B publishes some report with the same ID as used in the other jobs
5. Build C calls discoverReferenceJob again -> Reference Build switches to B but WarningsNG still uses A.

Behavior before the switch to Forensics API was that Job C's delta would have pointed to Job B as soon as it published the report. Now, even after calling discoverReferenceJob, it doesn't update.

The reference build is correctly set to the latest completed one, but warningsNG sticks with the one found when discoverReferenceBuild was called the first time.

-> Updating WarningsNG breaks some pipeline logic from us.