Dashboard: history stack for undo/redo

For undoing and redoing actions:

One possible solution is to create an IFolder stack of size ~20 (for 20 actions). For each action, eg Move, Rename, etc., push the root onto the stack. On undo, assign the last state to the root which will save to local storage, update dashboard, etc. Similar for redo, and add event listener for keybindings.

Start by locating IFolder and the handlers for actions such as Move and Rename, then trace how the root is saved to local storage and the dashboard is updated. Review the existing keybinding event listeners. Done means a bounded history supports undo and redo for these actions while preserving persistence and dashboard updates.

Written by the indexing model from the issue text.