refactor(table): preserve generic typing across forwardRef export

[leno23]

Motivation

• Ensure the Table component preserves generics across the forwardRef boundary so consumers can write <Table<User>> and get correct compile-time inference for columns, rowKey, sorter, and render.
• Replace fragile as-based indexing patterns with safer generic indexing so column keys, renderers and filters receive precise T[K]-typed values.
• Tighten internal state typings to reflect per-row keys and avoid runtime/TS surprises when filtering or sorting.

Description

• Introduced a generic internal implementation TableInner<T extends Record<string, unknown>> and export a typed wrapper via export const Table = forwardRef(TableInner) as TableComponent to preserve external generic inference in JSX. (file: packages/ui/src/components/data/Table.tsx)
• Added type TableKey<T> = Extract<keyof T, string> and changed TableColumn to TableColumn<T, K extends TableKey<T> = TableKey<T>> so key: K and render receives value: T[K] for accurate typing.
• Replaced unsafe accesses like record[column.key as keyof typeof record] with record[column.key] and updated filtering/sorting state to TableKey<T>-based types (sortKey, filterMap, visibleMap).
• Small runtime-safe refactor to extract sorter before invocation to avoid optional invocation errors and adjusted React import types for stronger typing.

Testing

• Ran type checking with npm run typecheck:ui and it completed successfully.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9274f38602

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore support for non-data display columns

Narrowing TableColumn.key to K extends Extract<keyof T, string> turns a previously supported pattern into a compile-time error: columns used only for UI actions (for example { key: 'actions', render: (...) => ... }) no longer type-check unless 'actions' exists on every row type. The previous API explicitly allowed keyof T | string, and the runtime logic still renders such columns, so this is a source-compatible regression for existing consumers upgrading the library.

Useful? React with 👍 / 👎.