Expose named project statuses and support status filtering

[FelixLisczyk]

Problem

Project responses currently expose only Linear’s deprecated scalar state field, which represents the status type rather than the named status. As a result, projects such as In Progress and On Hold—both of which may have type started—cannot be distinguished.

The CLI also does not support filtering project lists by named status.

Changes

This PR:

• Exposes the project status object with id, name, and type.
• Preserves state as a backward-compatible alias for the status type.
• Renders named statuses in human-readable project output.
• Adds --status filtering to linear projects list.
• Supports comma-separated, case-insensitive status names with whitespace trimming and deduplication.
• Rejects empty, unknown, ambiguous, and archived-only status filters clearly.
• Applies filtering before the requested --limit.
• Supports status filtering consistently for team-scoped and --mine project lists.
• Preserves existing team/default-team precedence and --state mutation behavior.
• Adds mutation result support so project state updates can expose the returned named status.
• Adds client, service, CLI, formatter, GraphQL, compatibility, and pagination tests.

Example:

linear projects list --team TL --status "In Progress"
linear projects list --team TL --status "In Progress, On Hold"

Testing

• Adds automated coverage for project status decoding and JSON output.
• Adds filtering, normalization, validation, duplicate, archived, and limit-ordering tests.
• Adds team-scoped and --mine service/CLI coverage.
• Adds text-rendering and legacy state fallback tests.
• Adds mutation response compatibility tests.