[Lens] Disable the global timepicker if user is using an index pattern without primary time field, and visualizing data without time

[bhavyarm]

Blocked on #100858

Kibana version: 7.9.0 BC2

Browser version: chrome latest

Describe the bug: If user is using a index pattern which is created without timefilter to create lens viz - lens app displays the global timepicker. But the visualization itself displays all the documents in that index pattern.

Though this is behaving as intended - having the time picker makes the user think that, user can filter the docs based on the time field.

Steps to reproduce:

1. Create an index pattern without specifying a timefilter.
2. Click on visualize->create->lens->pick the index pattern without the timefilter
3. Lens displays the global time picker

Expected behavior: Lens shouldn't display the global time picker (or let the user know whats happening)

Screenshots (if relevant):

[bhavyarm]

CC @wylieconlon

[elasticmachine]

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

[wylieconlon]

Recategorizing this as a minor bug because this used to work correctly, but now it doesn't

[timroes]

I am uncertain about the bug behavior in general here. Since Lens does support binding any date field to the time picker, by using it in the visualization (whether the index has a default time field or not), we need the time picker in case a field is bound. What do we think is the correct behavior here? Make sure we're only enabling the date picker, as soon as the index pattern either has a time field OR a time field got dropped into the visualization (that is bound to the timepicker, i.e. used in a date histogram)?

[flash1293]

What do we think is the correct behavior here? Make sure we're only enabling the date picker, as soon as the index pattern either has a time field OR a time field got dropped into the visualization (that is bound to the timepicker, i.e. used in a date histogram)?

I think this behavior would make sense. As soon as it can be used, it will become active.

[flash1293]

I looked into this and we could implement this similar to showNoDataPopover, but it will become much easier once #100858 lands because by then it will be a simple selector on the state instead of passing it up from the editor frame to the app in a weird way.

Let's wait until this is merged before fixing this bug.

[mbondyra]

Reserving for mob-programming session.