[Lens] Extends Axis bounds for XY chart when using Interval operation

[dej611]

Summary

Partially fixes #129308

This PR introduces the ability to extends or filter axis bounds when using the Interval operation on XY charts.
The code has been refactored to provide some shared functions and components for the feature.
The feature is available under the visualization axis controls and is set by default to Data:

Switching to Custom will show a new range input prefilled with existing bounds:

Notes

This implementation is very limited as it works only on the client side and for XY chart types.
Prior of this PR other approaches have been attempted which led to problems:

• Use ES to extends the Interval agg and produce all the buckets: [Lens] Extend bounds for Interval operation #132619
  • The main issue here is that composing the agg would produce a table with partial rows and some special code has to be written to handle it at visualization level anyway
• A heatmap version has been implementation as well on this branch but there's currently a limit on the elastic-chart side to force the chart to accept XY custom domain

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

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

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

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[flash1293]

Looks almost good to me, noticed one small bug

[flash1293]

When switching from custom to data, this check is applied to undefined/undefined which is preventing an actual state change (the chart doesn't update). We should only validate for "custom" extends

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: d77f50f
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
lens	921	926	+5

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
expressionXY	137	138	+1
lens	515	517	+2
total			+3

Async chunks

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

id	before	after	diff
expressionXY	96.5KB	96.7KB	+189.0B
lens	1.2MB	1.2MB	+3.7KB
total			+3.9KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
expressionXY	32.9KB	33.0KB	+172.0B

Unknown metric groups

API count

id	before	after	diff
expressionXY	147	148	+1
lens	592	594	+2
total			+3

History

• 💚 Build #50409 succeeded 920182c
• 💚 Build #50187 succeeded 7329f12
• 💚 Build #50141 succeeded 5a62a85
• 💔 Build #50121 failed 6a0e634
• 💔 Build #50104 failed f931f54

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

[dej611]

@flash1293 it should be fixed now

[flash1293]

Tested and works as expected, LGTM. Great feature!