Task Prioritization

**Is your feature request related to a problem? Please describe.**
Label Studio currently assumes FIFO (first-in, first-out) task presentation. While this works for some workflows, it limits flexibility when urgent, high-value, or model-critical tasks need to be labeled quickly. Without prioritization, important work is delayed, slowing model iteration, wasting reviewer time, and making it harder for project managers to pivot to high-impact tasks mid-project. In large projects, the inability to surface critical items first reduces efficiency and responsiveness.

**Describe the solution you'd like:**
Implement a Task Priority mechanism at the project level and/or as task metadata.

**Key Features**

**Priority Attribute**
- Integer range or enum (low, normal, high, blocker).
- Stored in task metadata, editable in the UI, available via API, import, and export.

**Project-Level Control**
- Setting to enable “Priority-based task ordering” for “Next Task” and queues.
- Secondary sort options (e.g., priority → created_at).

**Manual Assignment**
- Bulk actions in Data Manager: “Set Priority…”.
- Inline editing on task rows.
- API endpoint for batch updates.

**Automatic Assignment**
- Rules based on model predictions, metadata, or webhooks.
- Example: if prediction.uncertainty > 0.6, set priority = high.

**UI Enhancements**
- Priority column in task table (sortable/filterable).
- Priority indicator badge in the labeling UI.

**Describe alternatives you've considered**
- Creating multiple projects to split high- and low-priority tasks (increases management overhead, loses shared context).
- Using filters in Data Manager to manually surface important tasks (manual and error-prone).
- Pre-processing tasks before import (not dynamic for ongoing projects).

**Additional context**
In active projects, priorities often shift, a built-in prioritization system allows teams to adapt quickly without re-structuring the entire project.