Better management of the 200 page views/day limit in WebPageTest

[phacks]

Today, the majority of “Failed audits” is due to the project reaching the limit of 200 page views / day imposed (rightly) by the WebPageTest API.

There should be a better way to handle that than what we do right now, which is “keep trying to run audits on a fixed schedule (3x per day, 3 runs per audit) and if it fails so be it”.

Possibly an interface that would let project admins choose how they spend their tokens? I drew up a quick mockup:

Excalidraw source

Note: for private WebPageTest instances, there is no upper limit on the number of pageviews (to the best of my knowledge). We should think about what to do in that case (let an admin set an arbitrary limit? Set no limit?)