Look into refactoring or rewriting the accessibility hooks/utils for keyboard movement in widgets

[mlaursen]

The useKeyboardMovement, useActiveDescendantMovement, and useFocusMovement were an attempt at implementing some required accessibility helpers for different widgets. Since I wanted most of the movement utils to support typeahead movement as well, lots of components have a really weird and annoying api of stuff like getItemLabel and getItemValue. This kind of ruins the Menu component (and components that use the Menu) so it would be great to find a different way to implement this keyboard movement.

There's also some changes related to useFocusOnMount, usePreviousFocus, and useTabFocusWrap that could be combined and simplified to make updating other components easier and have a nicer API.