Ensure that re-starting a test job updates the report

Sometimes test job fail for a multitude of reasons, so it's useful to be able to re-trigger them and see the updated results in the report.

Unfortunately the report was not using any kind of consistent ordering, so it may have picked results from older jobs even if a new one had been completed for the same release/buildid/suites.

Tweak the report to pick jobs by the time the app gets notified about them, so that when a re-triggered job gets submitted its results override in the report the results from previous jobs.