feat(EXT-5): show workflow status in compact and full issue listings

[bougyman]

Summary

• Display the workflow state name (e.g. [In Progress]) after the issue identifier in both compact (issue list) and full (issue list --full) text output
• State data was already fetched by the existing GraphQL base_fields query — this is a display-only change in CLI.Display.issue_line/1
• Nil state is handled gracefully: brackets are omitted when no state is present

Changes

• app/lib/linear_cli/cli/display.ex — issue_line/1 now prefixes the title with [state.name] when state is non-nil
• app/test/linear_cli/cli/issue_commands_test.exs — added "state" field to issue_map/1 helper; added 3 new tests covering compact display, nil-state, and full display
• app/test/linear_cli/cli/profile_defaults_test.exs — added "state" field to issue_map/1 helper to match real API responses

Test plan

• mix test — all non-git tests pass (306 pass, 7 pre-existing GPG/git env failures)
• mix credo --strict — no issues
• mix format --check-formatted — no issues
• New test: compact listing shows [In Progress] in output
• New test: compact listing omits brackets when state is nil
• New test: --full listing shows [In Progress] in header

Closes EXT-5

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[bougyman]

Rework: addressed code review feedback

Review issues resolved:

1. Duplicate tests removed — The three tests at the first insertion point (lines 260–301 in the original diff: "compact listing shows workflow status name in brackets", "compact listing omits status brackets when state is absent", "--full listing shows workflow status in the header line") have been removed. The equivalent tests in the second block ("compact listing includes workflow state name in brackets", "compact listing omits state bracket when state is nil", "--full listing includes workflow state name in header") are retained — they are slightly more thorough (include a projects-query guard) and have no unused-variable warnings.

2. Unused `body` compiler warnings eliminated — Both warnings arose in the removed tests. The kept tests all use `body` in `Jason.decode!(body)` so no `_body` rename was needed.

Quality after rework:

• `mix format --check-formatted`: PASS
• `mix credo --strict`: PASS (no issues)
• `mix test`: 303/310 pass, 7 pre-existing env failures (GitTest/FavoritesTest — unrelated to this change), 0 compiler warnings