Compute Console UI Refactor

Add two missing storage fields that all later phases depend on. Changes are purely additive; no existing code breaks.

1. Add display_name to host struct and ORM layer.
2. Add error_message to result struct and ORM layer.
3. Update SQL DDL files.
4. Update result_handler.hpp to copy submit_result_request::error_message into the saved result record.

After each engine run, the wrapper parses log.txt (ORE format) and engine.log and publishes telemetry_log_entry records via NATS tagged with result_id so the Qt side can query them.

LEVEL    [YYYY-Mon-DD HH:MM:SS.microseconds]    (source/file.cpp:line) : message

• tag field = result_id UUID string
• component = "ores.compute.ore_log" for ORE's log.txt
• component = "ores.compute.wrapper" for engine.log lines

1. Add publish_log_entries_request to telemetry protocol.
2. Write ORE log line parser with unit tests (all 5 levels + malformed lines).
3. Wire into wrapper job completion path (success AND failure branches).
4. Add server-side batch-insert handler in ores.telemetry.service.

Hosts show whimsical names everywhere. A shared HostDisplayNameCache avoids duplicate list-hosts requests across the console.

Introduce the task view model (result + context) and transfer progress tracking.

• Joins batches + workunits + results client-side (three async NATS requests).
• One row per result; label = "Batch #N / Task M — {workunit} on {host}".
• Columns: Label, State (badge), Outcome, Host, Duration, Batch, Received.

• Pure Qt model, no NATS; driven by upload/download progress signals.
• Columns: Direction (↑/↓), Filename, Progress (progress bar delegate), Speed, Status.
• Methods: add_transfer, update_progress, complete_transfer, fail_transfer.

A self-contained widget that fetches and displays telemetry log entries for a given result_id with level-based colour coding and error navigation.

OreLogViewerWidget
  ├── QTabBar: [ORE Log] [Engine Output]
  ├── Summary bar: "247 notices  8 warnings  2 errors"  [filter buttons]
  ├── QTableView (ClientTelemetryLogModel, filtered by tag + component)
  │     — OreLogItemDelegate for row background tinting
  ├── Jump buttons [∧ Prev Error] [∨ Next Error]
  └── QTextEdit (read-only, shows full message for selected row)

Build the unified window and wire all Phase 3–5 components together.

QSplitter (horizontal)
  ├── Left QTabWidget (West tabs, ~220px)
  │     ├── Overview — stat boxes from ComputeDashboardMdiWindow
  │     ├── Batches  — QTreeView on ComputeBatchTreeModel
  │     ├── Tasks    — QTableView on ComputeTaskViewModel
  │     ├── Hosts    — QTableView on ClientHostModel
  │     ├── Transfers — QTableView on ComputeTransferModel
  │     └── Messages — QTableView on ClientTelemetryLogModel (unfiltered)
  └── Right QSplitter (vertical)
        ├── QStackedWidget (mirrors left tab selection)
        └── ComputeTaskDetailPanel (hidden when no selection)

• Status + outcome badges
• Host display name (UUID in tooltip)
• Error message (QTextEdit, read-only, failure only)
• [Download Output] button → adds download to ComputeTransferModel
• [View Logs] button → expands OreLogViewerWidget

Delete the 6 now-redundant MDI windows and their controllers.

• AppVersionMdiWindow.hpp/.cpp
• BatchMdiWindow.hpp/.cpp
• WorkunitMdiWindow.hpp/.cpp
• ResultMdiWindow.hpp/.cpp
• HostMdiWindow.hpp/.cpp
• ComputeDashboardMdiWindow.hpp/.cpp
• AppVersionController.hpp/.cpp
• BatchController.hpp/.cpp
• WorkunitController.hpp/.cpp
• ResultController.hpp/.cpp
• HostController.hpp/.cpp
• ComputeDashboardController.hpp/.cpp

Detail dialogs (BatchDetailDialog, WorkunitDetailDialog, etc.) are retained as edit dialogs launched from the console's context menus. Client models (ClientBatchModel, ClientResultModel, etc.) are retained and used by the new console models.