feat: per-project workflow settings, statistics and "my work" home

Per-project settings (owners/admins, «Configuración» tab):
- Statuses with category (TODO, IN_PROGRESS, QA, DONE, CANCELLED), colour and
  "requires reason"; configurable transitions; ticket types (icon, colour) and
  areas. Defaults are the previous fixed values; projects created before keep
  them without migration.
- Values are archived, never deleted: tickets, history and statistics keep
  referring to them. Validated in the domain (ProjectSettingsChangedEvent).
- Releases, board, tracking and "my work" use categories, so custom statuses
  keep working. Status changes carry name/category metadata for history.
- GraphQL: status/type/area are strings (breaking for clients sending enum
  literals); Project.settings, updateProjectSettings, statusCategory,
  myIssues(categories). REST: PUT /projects/{project}/settings, category filters.
- Read model: statusCategory on issues (backfilled at startup).

Statistics («Estadísticas» tab):
- New issue_timeline projection; pure functions compute created vs resolved,
  cumulative flow, cycle/lead time (avg + p85), throughput per person, QA
  pass/fail and release burnup. GraphQL Project.analytics(days),
  Release.burnup; REST /projects/{project}/analytics, /releases/{id}/burnup.
- Web: SVG charts with validated light/dark palette, crosshair tooltip,
  keyboard navigation, legend and data table.

Home "Mi trabajo": my open tickets across projects grouped by category (QA
failures first), tickets waiting for QA, upcoming releases and "Ir a…".

Tests: domain/application specs, e2e scenario for settings and analytics,
facade tests. Docs, READMEs, schema.gql/openapi.json and Word/PDF updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

libs/web/tracker/domain/src/lib/models/enums.ts

@@ -1,18 +1,13 @@
-export enum IssueType {
-  BUG = 'BUG',
-  FEATURE = 'FEATURE',
-  UI_CHANGE = 'UI_CHANGE',
-  TASK = 'TASK',
+/**
+ * What a status means, whatever each project calls it (statuses, ticket types
+ * and areas are per-project settings, see ProjectSettings).
+ */
+export enum StatusCategory {
+  TODO = 'TODO',
+  IN_PROGRESS = 'IN_PROGRESS',
   QA = 'QA',
-}
-
-export enum IssueArea {
-  FRONTEND = 'FRONTEND',
-  BACKEND = 'BACKEND',
-  MOBILE = 'MOBILE',
-  QA = 'QA',
-  DESIGN = 'DESIGN',
-  DEVOPS = 'DEVOPS',
+  DONE = 'DONE',
+  CANCELLED = 'CANCELLED',
 }
 
 export enum IssuePriority {
@@ -23,18 +18,6 @@ export enum IssuePriority {
   CRITICAL = 'CRITICAL',
 }
 
-export enum IssueStatus {
-  BACKLOG = 'BACKLOG',
-  TODO = 'TODO',
-  IN_PROGRESS = 'IN_PROGRESS',
-  IN_REVIEW = 'IN_REVIEW',
-  READY_FOR_QA = 'READY_FOR_QA',
-  IN_QA = 'IN_QA',
-  QA_FAILED = 'QA_FAILED',
-  DONE = 'DONE',
-  CANCELLED = 'CANCELLED',
-}
-
 export enum IssueLinkType {
   BLOCKS = 'BLOCKS',
   DEPENDS_ON = 'DEPENDS_ON',