Run scheduling changes - run state READY

This week we’re introducing the READY state in to the run state progression.

Any newly queued runs will be evaluated to determine if they can be moved the “READY” state. However the scheduler will process both “QUEUED” and “READY” runs while the migration is taking place.

Moving forward, the “QUEUED” state will mean that a run is not ready for scheduling, as it’s either blocked, waiting for dependencies to finish, or isn’t approved. The “READY” state will mean that a run is ready for scheduling and is waiting for a worker to pick it up.