Currently, all URLs are run once a day. This milestone changes that and allow that to be configurable. It allows an admin to specify a list of URLs to be grouped together in a queue (instead of just default .all() queryset), and it allows that group/job to be specified with a frequency.

This has a lot of dependencies, but this is a major end-game goal we are striving for. When you put in 10s to 100s of thousands of URLs, they are probably not all needed to run daily, but rather certain subsets run at different times/frequencies.

A job is a named set of urls run together in a queue.

The job should have a description and an "owner" (who wanted it) and should be able to set frequency of job and what urls are in it's set.

This relies on comms/APIs and Lighthouse run config profile models and worker monitoring/management... a bunch of dependencies here that need to have issues added for.