Summary

Implements a priority queue system for provisioner jobs to ensure human-initiated workspace builds are processed before prebuild jobs, improving user experience during high queue periods.

Changes

• Database: Added priority column to provisioner_jobs table with migration
• Queue Logic: Updated AcquireProvisionerJob query to order by priority DESC, created_at ASC
• Priority Assignment: Human-initiated jobs get priority 1, prebuilds get priority 0
• API: Exposed priority field in SDK and conversion functions
• Testing: Added comprehensive test to verify priority queue behavior

How it works

1. When creating provisioner jobs, the workspace builder checks if the initiator is the PrebuildsSystemUserID
2. Human-initiated jobs get priority = 1, prebuild jobs get priority = 0
3. The AcquireProvisionerJob query now orders by priority first, then creation time
4. This ensures human jobs are always acquired before prebuild jobs, regardless of creation time

Testing

• Added unit test that verifies priority-based job acquisition
• Test creates both human and prebuild jobs and confirms acquisition order
• Existing tests should continue to pass as the change is backward compatible

Impact

• Users: Faster workspace build times when prebuilds are queued
• System: No performance impact, just changes query ordering
• Backward Compatibility: Existing jobs get default priority 0, new logic applies to future jobs

Fixes the issue where prebuilds could delay human-initiated workspace builds during busy periods.