feat(frontend): allow users to customize the sorting of proposed changes list
Merged
BI
4mo ago+255+255+012345678901234567890123456789-116-116-012345678901234567890123456789
Issue: #9915
Why
The proposed changes list is ordered newest to oldest, and there is no way to change that. Goal: let users sort by any sortable field, in either direction. Closes #9915
What changed
- A Sort picker in the toolbar, covering every sortable field (incl. Created at / Updated at), either direction, persisted in the sort query param.
- The table headers sort too — a field chip opens the column-header menu, which offers sorting and filtering for that field.
- A row surfaces its update date only while the list is ordered by it.
- With no sort chosen, the list still defaults to newest created first.
Implementation notes kept to three lines (TableColumnHeader reuse, PROPOSED_CHANGE_DEFAULT_SORT as a client-side default since CoreProposedChange has no order_by, sort in the
query key). Review/test/rollout sections unchanged from before, minus the padding.