feat(workflow): add WorkflowListener bridging WP hooks → runner

[mpge]

Summary

Final piece of the workflow stack for WordPress. Subscribes to the existing escalated_* do_action hooks (priority 50) and routes each to the canonical workflow trigger name, then delegates to WorkflowRunnerService::run_for_event.

Hook → trigger mapping

Matches WorkflowEngine::TRIGGER_EVENTS:

WP hook	Workflow trigger
escalated_ticket_created	ticket.created
escalated_ticket_updated	ticket.updated
escalated_ticket_status_changed	ticket.status_changed
escalated_ticket_assigned	ticket.assigned
escalated_ticket_reopened	ticket.reopened
escalated_reply_created	reply.created
escalated_tag_added/_removed	ticket.tagged
escalated_department_changed	ticket.department_changed

Wiring

Registered from Escalated::boot() alongside BroadcastService. Hook failures are caught (warn-logged when WP_DEBUG is on) so one bad workflow never blocks the mutation that fired the hook.

Complete chain

TicketService mutation → do_action('escalated_*')
  → WorkflowListener callback
  → WorkflowRunnerService::run_for_event
  → WorkflowEngine (conditions) + WorkflowExecutorService (actions)
  → workflow_logs audit row

Dependencies

• Stacked on feat(workflow): add WorkflowRunnerService for event-driven workflow firing #29 (feat/workflow-runner), which is stacked on feat(workflow): add WorkflowExecutorService for action dispatch #28 (feat/workflow-executor).
• Merge order: feat(workflow): add WorkflowExecutorService for action dispatch #28 → feat(workflow): add WorkflowRunnerService for event-driven workflow firing #29 → this PR.

Test plan

• 6 WP integration tests covering hook → log-row creation for each trigger + the bad-argument tolerance path
• CI green (won't trigger against stacked base until rebased)