[Menu][base] Add the resetHighlight action

[michaldudak]

This change enables solving the problem described in #36857 (review).

The issue was that after resetting the filter, the highlight remained at the first filtered item.
There are cases where this behavior is desired - for example, when lazy loading more options, we don't want the highlight to jump to the beginning. That's why I decided to leave the decision to reset the highlight to the developer. See https://codesandbox.io/s/cranky-jennings-954ghk?file=/demo.tsx for an example of how to solve it.

Initially, we discussed exposing just the high-level functions in the actions ref of the Menu (resetHighlight). However, this may not be enough as we need more actions to be dispatched, such as keyDown and buttonClick (they are used to implement our demos, so developers will likely need to use them). When we implement the MenuButton, we probably won't have to expose so many actions.
I ended up exposing both resetHighlight (for ease of use) and dispatch (for completeness). Let me know if you think it's redundant. I'm not sure what's the best option here.

Closes #36800

[mui-bot]

Netlify deploy preview

https://deploy-preview-37392--material-ui.netlify.app/

@material-ui/unstyled: parsed: +0.27% , gzip: +0.24%
@mui/joy: parsed: +0.10% , gzip: +0.09%

Bundle size report

Details of bundle changes

Generated by 🚫 dangerJS against 233ea5c

[siriwatknp]

👍 LGTM. Regarding the demos, I think they need to be simplified. It's quite intimidating with a lot of useRef at the moment.

[michaldudak]

Regarding the demos, I think they need to be simplified. It's quite intimidating with a lot of useRef at the moment.

Yeah, I agree. The major reason for this is the lack of the MenuButton component. Once we have this, demos will become much simpler.