Fix Taskboard thread and workflow context

[MateoCerquetella]

What changed

• Open Taskboard on the project associated with the source/current bb thread when that project still exists.
• Preload each provider workflow before enabling Kanban moves so zero-count status columns stay visible.
• Keep provider statuses in the configured order before, during, and after a move.
• Use a backlog-first default workflow: Backlog, Todo, In Progress, In Review, QA, then the remaining provider statuses.
• Wait for per-project board settings before rendering and cover thread selection plus workflow stability with focused tests.

Why

The persisted Taskboard subpath could override the thread project, while Kanban learned provider statuses only after interacting with a card. That made empty columns disappear and allowed the lane set/order to change during drag-and-drop. The prior default also started at In Review instead of following the delivery flow from Backlog.

Validation

• npm run check
• Live bb check from the current bb-plugins thread routed to its matching Taskboard project.
• Live Bandely Kanban showed: Backlog (2), Todo (0), In Progress (0), In Review (1), QA (0), Ready for Release (0), Duplicate (0), Done (0), Canceled (0).
• Keyboard pickup/cancel preserved the lane order without writing to Linear.