[base-ui][material-ui][joy-ui][useAutocomplete] Correct keyboard navigation with multiple disabled options

[VadimZvf]

Fixes #39281

The current implementation of the useAutocomplete hook has a little bug.
The looped navigation in the option list doesn't work properly.
When user navigates via keyboard in the select component with disabled options, he needs to press the down arrow twice if disabled option is in the end of the list.

Scenario:

1. The user focused on the last not disabled option.
2. User press on the down arrow button - the focus disappears (bug)
3. After second press the focus appears on the first list option

Example before fix:

Screen.Recording.2023-09-03.at.14.26.02.mov

After fix:

Screen.Recording.2023-09-03.at.14.48.08.mov

Issue codesandbox: https://codesandbox.io/s/agitated-frost-qcdgxt?file=/Demo.tsx

Fix codesandbox: https://codesandbox.io/s/autumn-wood-tcc2jl?file=/package.json
Another fix of #39281: https://codesandbox.io/s/https-github-com-mui-material-ui-issues-39281-5g5qsf?file=/Demo.tsx

[mui-bot]

Netlify deploy preview

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

Bundle size report

Details of bundle changes (Toolpad)
Details of bundle changes

Generated by 🚫 dangerJS against 577d849

[mnajdova]

The logic looks good to me. Regarding the tests, so far most of the tests were added in Material UI's Autocomplete component, as a way to test more the end to end behaviour, however this will likely change long term considering all components will use the hook, it would mean that we need to replicate the tests in all components. cc @michaldudak for thoughts on this.

[michaldudak]

The goal is to test the Base UI unstyled component thoroughly, so we have coverage of both component and a hook. Material UI and Joy UI could have just their extensions tested.
Now, with Autocomplete, we're not there yet because we don't have the unstyled component yet, and we want to create another version of the hook. For now, I'd stick to testing Material UI's Autocomplete.

[VadimZvf]

Hi @mnajdova !
Can you have a look at my PR one more time, please?
I've moved tests to Autocomplete components tests.

[ZeeshanTamboli]

@VadimZvf Looks good! Also nice tests 👍 I've left some minor comments.

[ZeeshanTamboli]

Your PR fixes #39281. I linked it in the description.

[VadimZvf]

Thank you for reviewing 🙏

CI task has failed, seems to me like something with the CI tool

[ZeeshanTamboli]

@VadimZvf Looks good! Thank you for your contribution!