promote(customer-priority-bump): apply 'priority' label instead of Priority field (D5)

[LukasWodka]

Summary

Promotes #84 to main so the live reusable workflow stops writing the soon-to-be-deleted Priority project field.

customer-priority-bump.yml runs from @main (that's what the per-repo callers reference), so the field-writing version was still the one executing in production. This copies develop's label-based version (gh issue edit --add-label priority) onto main verbatim.

Prerequisite for deleting the Priority project field (part of #1273 — field cleanup, D4/D5/D12: one priority source = the priority label).

Test plan

• Content is identical to the already-reviewed fix(customer-priority-bump): apply 'priority' label not the field (D5, unblocks Priority-field deletion) #84 (merged to develop). Single-file promotion.
• After merge: labeling any issue from:customer adds the priority label instead of touching the (deleted) field.

Part of #1273.

---

Note

Low Risk
Narrow CI automation change aligned with board cleanup; no app auth or data paths, though mis-timed merge could briefly conflict with deleting the Priority field.

Overview
Promotes the D5 behavior to main for the reusable customer-priority-bump workflow so production stops updating the deprecated Priority project field.

When from:customer is applied, the workflow now runs gh issue edit --add-label priority instead of GraphQL against Project V2 (field lookup, retry loop for project item registration, and updateProjectV2ItemFieldValue). Unused workflow env vars tied to the old path (ORG, PROJECT_NUMBER, PRIORITY_NAME) are removed; workflow_call inputs like target-priority remain but are no longer used by the step.

^{Reviewed by Cursor Bugbot for commit 9c1103e. 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 9c1103e. Configure here.}

[LukasWodka]

skip-fr-gate — written reason (RFC-0008 D27): legitimate release-mechanics promotion. This copies the already-reviewed #84 (customer-priority-bump label fix — merged to develop, Bugbot-clean) verbatim onto main, so the live @main reusable workflow stops writing the Priority project field ahead of its deletion (#1273 / D5). The single promotion commit carries no (#N) because it's a direct file copy, which is why the gate correctly flags it as unattributable. .github has no deployable environment to functional-review on, so the FR-ladder doesn't map — this is exactly the "legitimate release-mechanics commit" the gate names.