Add testing-latency metrics
Right now, we are not keeping track of the testing latency properly, which means it is hard to hold us accountable for not providing timely results.
To avoid hammering the patchwork's REST API on every page load, let's create a python script that can live in this repo that would poll patchwork's events (patchwork-fdo/patchwork-fdo#24 (closed)) and create a json file that can be uploaded to the public website. This file can then be used on the client side to visualise the latency per project.
For the visualisation, we could use D3's violin plots, along with some combo boxes to set the project, test result, and the starting/ending dates for the data along with the period.