fix(frontend): render CANCELLED run status instead of crashing the detail page

[tomny-dev]

Summary

The automation detail page crashes with Cannot read properties of undefined (reading 'style') whenever an automation has a cancelled run. The automations list page works; only the detail view breaks.

Root cause

The backend AutomationRunStatus enum includes CANCELLED (openhands/automation/models.py), but the frontend was out of sync:

• frontend/src/types/automation.ts — AutomationRunStatus was missing CANCELLED.
• RunStatusBadge — statusConfig had no CANCELLED entry.

So for a cancelled run, RunStatusBadge evaluates:

const config = statusConfig[status]; // statusConfig["CANCELLED"] -> undefined
// ...
className={`... ${config.style}`}    // undefined.style -> throws, gives error screen

Because status is cast from the API response without runtime validation, the exhaustive Record<AutomationRunStatus, ...> type couldn't catch this frontend/backend drift at compile time.

Fix

• Add CANCELLED to the frontend AutomationRunStatus enum so it matches the backend.
• Add a CANCELLED badge config (neutral style) and icon (reuses the x-circle icon alongside FAILED).
• Add the AUTOMATIONS$DETAIL$CANCELLED i18n strings for all locales.
• Add a RunStatusBadge test for the cancelled status.

The generated src/i18n/declaration.ts (gitignored, produced by make-i18n) picks up the new key automatically during prelint/build.

Testing

• node scripts/make-i18n-translations.cjs regenerates declaration.ts with AUTOMATIONS$DETAIL$CANCELLED.
• Added unit test renders <RunStatusBadge status={AutomationRunStatus.CANCELLED} /> without throwing.