v3: correctly handle triggering tasks prior to deploy

[nicktrn]

Problem

It's possible to trigger a task before deploying it. This can happen because the deploy step hasn't completed yet, or because it wasn't started.

Solution

Triggering tasks prior to deploy will put the respective runs in a WAITING_FOR_DEPLOY state. This state prevents execution attempts. It's cleared as soon as the task has been deployed and is enqueued again for immediate execution while maintaining the correct order.

This also adds:

• Sensible order for tasks filter items 🔤
• Ability to enqueue with delays
• Fix a race condition where the run wasn't created yet prior to dequeuing the execute message

[changeset-bot]

⚠️ No Changeset found

Latest commit: 60e178f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR