feat(manager): persist access-key table sort preference

[whoalin1]

Summary

Closes #1909

Access-key table sort (column + direction) reset every time the Manager was reopened.

• Persist sort column id and direction in localStorage, keyed per server id.
• Restore the preference when the server view becomes ready.
• Update the stored preference whenever the user changes sort.

Test plan

• Open a server, sort keys by name or data used
• Quit / reload Manager → same sort is applied for that server
• Sorting another server does not overwrite the first server's preference

[greptile-apps]

Confidence Score: 4/5

[Low risk] Saves table sort preference to browser storage.

The PR appears safe to merge, with a fallback for stale saved values and tests worth adding.

Findings

1.  Old sort choices stop working ▶
2.  Saved sorts lack tests ▶

Summary

The Outline Manager now remembers the access-key table’s sort column and direction for each server. It saves the choice in localStorage and restores it when the server view becomes ready.

• The access-key table keeps its sort for each server.

_{Reviews (1) · Last reviewed commit: "feat(manager): persist access-key table ..." · Reviewed by Greptile}

[greptile-apps]

Old sort choices stop working

If an update removes or renames a sortable column, _restoreAccessKeySortPreference() still applies its saved name. The table then shows the keys unsorted without clearing that choice. Check the saved column and direction before applying them, and use a default when either is no longer valid.

Knowledge Base Used: Server operations console

[greptile-apps]

Saved sorts lack tests

The new save-and-restore path has no test for reopening the Manager or keeping two servers’ choices separate. Add coverage for both flows so a later change to view startup or server selection does not silently undo this feature.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!