fix(customer-priority-bump): apply 'priority' label not the field (D5, unblocks Priority-field deletion)

[LukasWodka]

D5: priority is a binary label now, not a project field. This reusable still set the Priority field — which would break once the field is deleted (I've deleted 8 of the 9 dead fields; Priority is the one held back on this).

Rewrites it to gh issue edit --add-label priority. Merge → promote to main → then I delete the Priority field.

---

Note

Low Risk
CI-only change to how customer issues are marked; no app runtime impact, though callers expecting P1 on the project board will now only get the label until they update filters/process.

Overview
D5: Customer-flagged issues are now escalated via a priority issue label instead of setting the org project’s Priority single-select field.

The reusable customer-priority-bump workflow drops the GraphQL project lookup, retry loop for project items, and updateProjectV2ItemFieldValue mutation. On from:customer, it runs gh issue edit --add-label priority using the existing PROJECTS_KANBAN_TOKEN. Workflow comments and step naming reflect the new behavior.

Callers can still pass project-number, org, and target-priority; those inputs are no longer used by the job (only trigger-label behavior remains).

^{Reviewed by Cursor Bugbot for commit e1854f1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LukasWodka]

bugbot run

[LukasWodka]

👋 Heads-up — Code review queue is at 39 / 30

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

• averaging-service#207 — Promote develop → staging · author: @shujaatTracebloc · no reviewer assigned
• backend#1201 — docs(rfc): Data spaces & federated dataset composition (draft) · author: @LukasWodka · no reviewer assigned
• backend#1217 — docs(rfc): Dataset integrity & score reproducibility (draft) · author: @LukasWodka · no reviewer assigned
• backend#1228 — Promote develop → staging · author: @shujaatTracebloc · reviewer: @saadqbal
• backend#1244 — fix(experiments): surface save-time failures as 5xx + guard new NOT NULL columns · author: @LukasWodka · reviewer: @saqlainsyed007
• backend#1251 — docs(bugbot): add .cursor/BUGBOT.md project context (#930) · author: @LukasWodka · no reviewer assigned
• backend#1254 — docs(pr-template): owner-qualify cross-repo closing keywords · author: @LukasWodka · no reviewer assigned
• backend#1259 — docs(rfc): qualified RFC identifiers + org-wide index · author: @LukasWodka · no reviewer assigned
• backend#1261 — RFC-BACKEND-0008: board & process reset (decision RFC — for markup) · author: @LukasWodka · no reviewer assigned
• cli#397 — Release develop → main · author: @shujaatTracebloc · no reviewer assigned

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit e1854f1. Configure here.}