[Lens][Visualize] Reflect date/time filter to timepicker

[dej611]

Summary

Fixes #116752

This PR makes the inspector table aware of time fields when filtering.

I'm a bit two mind here for this fix, so I'll take the opportunity of this PR to discuss it:

• in Lens the timepicker is automatically bound to the current date histogram field
• in Visualize the timepicker is only bound to the default time filter

While for Lens it "feels natural" as the field and timepicker are bound to the same field, in Visualize it can feel strange to pick a value from another field and use it for the default field in the time picker.

Is that the desired behaviour?

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)

[dej611]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 6fd307a
• 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
data	101.5KB	101.7KB	+184.0B

History

• 💚 Build #15320 succeeded 2a9c71e

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

[flash1293]

As you said I think we can’t do this for visualize as it will be objectively wrong as it won’t filter correctly by the selected value (and it will also become problematic for Lens as soon as #118851 is implemented which is planned for 8.2) if we can’t make it behave right (maybe making the bound time fields part of the meta information of the table and looking them up from there to decide whether the filter should go into the time range or into a filter pill)I think the current behavior is better than the behavior of this PR.

Actually putting this information into the datatable meta information seems like a good approach to me because we will have this problem in general once we implement the issue linked above.

[dej611]

Ok, I'll close this in favour of a better fix with #118851