Menu: use ariakit types

[ciampo]

What?

Refactor Menu's types to re-use ariakit's types, and enhance prop descriptions.

Why?

• Aligning with how other ariakit-based components declare their prop types
• Better clarity when reading docs about Menu's props

How?

Importing and using type definitions from @ariakit/react

Next steps

• MIgrate Menu to auto-generated README
• move open-related props to popover component
• consider changing default modality, and add any extra props to MenuPopoverProps (eg. portal, preventBodyScroll ...)

Testing Instructions

• Make sure project builds without any TS error
• Compare the generated prop types in Storybook between this PR and trunk
• Smoke test component usages in Storybook and in the editor

[github-actions]

Flaky tests detected in bfc6593.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12455409108
📝 Reported issues:

• [Flaky Test] Navigates the items list via UP/DOWN arrow keys #64334 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js
• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

[ciampo]

Removed the extends syntax so that each component uses the correct ariakit types (ie. Menu.Item uses Ariakit.MenuItemProps, Menu.CheckboxItem uses Ariakit.MenuItemCheckboxProps, and Menu.RadioItem uses Ariakit.MenuItemRadioProps

[ciampo]

Added an explicit false value for the disabled prop — this is also reflected in the code when destructuring props

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ciampo <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.