Improve handling of CI jobs when a user has run out of CI minutes

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Currently when a user has run out of shared CI runner minutes any jobs that are created are left in the queue in a pending state. This has a few negative effects:

• Adds a lot of irrelevant jobs to the queue as they accumulate
• Masks our ability to see how long a job is in the queue on average
• Potentially uses up all the users new shared minutes as soon as they buy more

We need to explore some options for how to improve these scenarios.

CC @brendan @jhampton