fix: navigational dropdown back button bug

[dedarritchon]

Navigational Dropdown was presenting some buggy behavior, needing to click the back button twice to go back in some situations.

Cause

The old logic reset the stack when contentVersion changed but scheduled the auto-restore path by calling setAutoNavigateToSubmenuPath from inside the setViewStack functional updater. That’s nested state updates in one updater, which is easy to get wrong and can leave stack vs. path briefly inconsistent for children (e.g. submenu triggers firing auto-navigateTo at the wrong time). The “if top id === id, replace instead of push” block was papering over duplicate stack entries from that kind of race.

What we changed

viewStackRef
On each render, viewStackRef.current is set to the latest viewStack, so the layout effect can read the pre-reset stack reliably on the render where contentVersion just changed.

contentVersion useLayoutEffect
When the version actually changes (same guard as before with prevContentVersionRef):

Derive navigationPath from viewStackRef.current (slice of submenu ids after root).
Call setViewStack([root]) as a normal update.
If there is a path to restore, call setAutoNavigateToSubmenuPath(navigationPath) as a separate update, not from inside the stack updater.
So the fix is structural: same behavior intent, but without nesting one setter inside the other.

navigateTo when top.id === id
That branch stayed, but the idea is reframed: idempotent navigation to the current top view (updates getContent / parentTitle, avoids pushing another frame for the same id). It’s not framed as “contentVersion ran twice” anymore.