fix: apply lastReceived field format changes in custom feeds

[DragonBot00]

Summary

Fixes #5236

Problem

In custom (backend-persisted) feeds, changing the format of the lastReceived field via the column header dropdown had no visible effect. The format change appeared to succeed silently - no error was shown - but the column continued rendering timestamps in the previous format.

Root Cause

Custom feeds (non-static presets) use a backend API to persist column configuration, including columnTimeFormats. This is managed by the usePresetColumnState hook, which reads and writes format settings via usePresetColumnConfig. The AlertTableServerSide component correctly passes the synced columnTimeFormats to the table via table.options.meta.

However, the cell renderers in useAlertTableCols (inside alert-table-utils.tsx) read columnTimeFormats exclusively from React local storage via useLocalStorage -- a closure-captured value that is never updated when the backend state changes. This caused the visual display to remain stale even after the backend was successfully updated.

Fix

• Updated both time-aware cell renderers in useAlertTableCols (the lastReceived accessor and the generic date column renderer in filteredAndGeneratedCols) to prefer context.table.options.meta?.columnTimeFormats over the local storage fallback. This ensures custom feeds render using the authoritative, backend-synced format.
• Extended the TableMeta interface declaration in keep-ui/types/react-table.d.ts to include columnTimeFormats and setColumnTimeFormats, providing proper TypeScript typing for the table metadata already set by AlertTableServerSide.

Static presets and the deprecated AlertTable component are unaffected -- they do not set meta.columnTimeFormats, so the local storage fallback continues to apply.

Files Changed

• keep-ui/widgets/alerts-table/lib/alert-table-utils.tsx -- read columnTimeFormats from table meta when available
• keep-ui/types/react-table.d.ts -- extend TableMeta with columnTimeFormats and setColumnTimeFormats

[vercel]

@DragonBot00 is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[DragonBot00]

I have read the CLA Document and I hereby sign the CLA