Add team states command; list valid states on wrong --state

[schpetbot]

What

Adds linear team states [teamKey] to list a team's workflow states, and makes a wrong --state on issue create/issue update actionable.

Before, discovering valid state names meant a raw GraphQL query, and a wrong --state failed with a bare Workflow state not found: 'X' for team XX — no hint at the options.

Changes

• linear team states [teamKey] — falls back to the configured team like team members; prints a NAME/TYPE table sorted by position, or -j, --json as { nodes: [...] } (GraphQL field names/connection shape preserved). Reuses the existing getWorkflowStates helper — no new GraphQL/codegen.

• Actionable wrong-state error — issue create/issue update now fetch the states once, resolve against them, and on a miss throw an error whose suggestion lists the valid states and points at linear team states <TEAM>:

  ✗ Failed to update issue: Workflow state not found: 'notarealstate' for team CLI
    Valid states: "Backlog" (backlog), "Todo" (unstarted), … Run `linear team states CLI` to list them.
  

  Resolution moves to a pure resolveWorkflowState plus a shared workflowStateNotFoundError factory so both call sites stay identical and the matching logic is unit-tested; the fetched list is reused for the suggestion (no second round-trip).

Deliberately out of scope

The issue also hypothesized a raw TypeError for unknown teams. I verified this is not the case — team(id) is non-null in the schema and an unknown team already yields a clean Could not find referenced Team. — so no null guard was added. The --state help text was left unchanged to avoid churning the (width-sensitive, globally stale) generated skill docs; the enriched error is the load-bearing discovery path.

Tests

Unit tests for resolveWorkflowState (name/type precedence, duplicate-type ordering) and workflowStateNotFoundError (formatting, quote escaping, empty-states); command snapshots (table sorting, --json, configured-team fallback, empty, no-team error) plus a registration guard; and end-to-end enriched-error snapshots for both issue commands.

Fixes #210