v2.3.3

fix: list_tickets status label filter resolved the wrong result set

The label was passed raw to the API, which intval()s it: "New" became 0
and silently filtered on status ID 0 — asking for New returned every
Done ticket on the local test project (175 items, live-reproduced).

Labels now resolve to IDs server-side against the project's cached
status map (case-insensitive); CSV lists resolve token by token; unknown
labels error with the project's valid statuses (id + name); the server's
magic done/not_done values and numeric IDs pass through untouched.

Live-verified: status="New" → 101 New items (was 175 Done); unknown
label → actionable error listing valid statuses.