[Lens] Show validation feedback on top values out of bounds number of values

[dej611]

Summary

Fixes #105133

This PR adds some validation feedback around the Number of values input field for the Top values operation, when the user inputs a value either too high or low.

The error message is contextual and an explanation of the fallback is included:

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[dej611]

@elasticmachine merge upstream

[stratoula]

LGTM, I tested it locally and it works fine 😉
Just a comment here, I see that we have two cases of validations in Lens number inputs:

• if the user adds a value outside the predefined thresholds, we display an error message (like in this PR)
• If a user adds a value outside the predefined thresholds, we automatically change them to the accepted threshold. (for example in the legends popover number inputs)

Does it make sense to align the behaviors?
cc @MichaelMarcialis

[MichaelMarcialis]

Does it make sense to align the behaviors?

Excellent question, @stratoula. We absolutely should be aligning behaviors such as this when it makes sense to do so. And I agree with you in believing that this is indeed one of those situations.

For a tool like Lens, where configuration changes are reflected immediately on the visualization, anything we can do to avoid hitting users with error messages and asking them to perform unnecessary additional actions is preferable in my opinion. As such, I like the idea of automatically changing an invalid Number of values to a valid entry on blur.

For example, in the case of a user entry of 5000, this should automatically change to 1000 on blur. Similarly, in the case of a user entry of -5, this should automatically change to 1 on blur.

[dej611]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: d858671
• Storybooks Preview

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
lens	1.6MB	1.6MB	+844.0B

History

• 💚 Build #149700 succeeded d51f3dc
• 💚 Build #149355 succeeded a62afa9
• 💚 Build #148890 succeeded 7e6b08b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[mbondyra]

tested on Chrome, the behavior is aligned with the comments from the PR. code lgtm 🆗

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.