Log detail/expanded view renders Timestamp in raw UTC, while table/list view correctly converts to local timezone

[WeiJie-JL]

Describe the bug

In the log explorer, the table/list view correctly converts the Timestamp field to the browser's local timezone (e.g. Asia/Shanghai). However,
when clicking into a log row to view the detail/expanded view, the Timestamp field is displayed as raw UTC without any timezone conversion.

To Reproduce

1. Open log explorer and view any log table — Timestamp shows in local time (e.g. 10:23:15 for UTC 02:23:15)
2. Click into a specific log row to expand the detail view
3. The Timestamp field in the detail view shows raw UTC (e.g. 2026-06-15T02:23:15.895Z)

Expected behavior

The detail/expanded view should apply the same timezone conversion as the table view, displaying the Timestamp in the browser's local timezone.

Actual behavior

Timestamp in the detail view is rendered as-is from the API response (UTC), without any dayjs / date-fns / formatter conversion.

API response sample

{
  "Timestamp": "2026-06-15T02:23:15.895Z",
  "__hdx_timestamp": "2026-06-15T02:23:15.895Z",
  "ServiceName": "kuku-postgres001.gz.cvte.cn:5432",
  "meta": [{ "name": "Timestamp", "type": "DateTime64(3)" }]
}

Possible cause

The table view likely uses a timezone-aware formatter (e.g. dayjs(ts).format(...)) on the Timestamp column, while the detail/log-view panel renders the
raw string value directly without passing it through the same formatter.

Environment

- HyperDX version: (fill in)
- Browser timezone: Asia/Shanghai (UTC+8)

[satyasai1916]

Opened #2495 to fix the timezone mismatch in the log detail JSON viewer.