feat(autocomplete-core): add enterKeyHint option to manually set hint on virtual keyboards

[dhayab]

Summary

Currently we dynamically set the enterKeyHint property of the Autocomplete input, depending on whether there are results in collections and the items inside have URLs.

This can cause issues in multiple situations we don't have control over, one we have identified being customers using the Samsung keyboard on Android and have predictive input enabled.

We have a guard in place that works by identifying the type of device, but latest developments with the Android Chrome browser prevents retrieving the data we need, so we are less and less able to correctly activate this guard.

For customers who want to address this issue, and to keep accessibility benefit for others, this PR introduces an enterKeyHint prop on Autocomplete, that when defined, will take precedence over the current heuristics, and statically set the value on the Autocomplete input.

[dhayab]

Sadly HTMLElement['enterKeyHint'] is too broad, so I went for an explicit listing of allowed values, based on https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/enterkeyhint#values.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 07f9247:

Sandbox	Source
@algolia/autocomplete-example-github-repositories-custom-plugin	Configuration
@algolia/autocomplete-example-instantsearch	Configuration
@algolia/autocomplete-example-playground	Configuration
@algolia/autocomplete-example-preview-panel-in-modal	Configuration
@algolia/autocomplete-example-react-renderer	Configuration
@algolia/autocomplete-example-starter-algolia	Configuration
@algolia/autocomplete-example-starter	Configuration
@algolia/autocomplete-example-reshape	Configuration
@algolia/autocomplete-example-vue	Configuration