chore(desktop): upgrade Radix context menu

[matt2e]

Summary

• Upgrade Radix context-menu from 2.2.16 to 2.3.7.
• Pull the underlying Radix menu implementation from 2.1.16 to 2.1.24 and remove its now-duplicate older dependency graph from the lockfile.

The Move to section submenu in a channel context menu was observed flickering/disappearing briefly during startup, then settling after roughly 30 seconds. The behavior was not reproducible on current main, so this is a best-fit mitigation rather than a claim that the root cause is proven.

Buzz uses React 19. Radix issue #3963 documents an intermittent React 19 infinite re-render loop caused by unstable composed-ref identities, including in MenuSubTrigger. Radix menu 2.1.19 includes the corresponding fix; this upgrade moves Buzz through that fix to 2.1.24.

Related issue

• Buzz report: channel buzz-move-to-disappears, event 6ca216a355313fe032852f250cbafe1d40814382cbc2d0b7059dbac13038f398.
• No matching GitHub issue or dependency-upgrade PR was found.
• Remaining upstream risk: Radix #4036 is still open for a collision-flipped submenu whose stale pointer-grace direction can close it before a click lands under React 19.

Behavior changes

Radix's intervening context-menu releases intentionally change a few edge behaviors: menus now close when the window loses focus, an already-open menu reanchors to a subsequent context-menu event, long-press submenu state resets correctly, and Space/Enter from focusable descendants is no longer intercepted. No Buzz API changes were required, and 2.3.7 reverts the React Server Component compatibility regression from intermediate releases.

Because the dependency backs Buzz's shared desktop context-menu wrapper, these behavior fixes apply to all desktop context menus, not only the channel menu.

Testing

• ./bin/just ci
• Targeted Playwright interaction probe against the upgraded build: right-opening and forced collision-flipped left-opening Move to section submenus both remained open through delayed capability loading, accepted pointer movement into the submenu, and completed the channel move.
• Screenshots are not applicable; there is no intended visual change.