[Rules] Add validation to prevent selecting a data view without a time field in "Elasticsearch query" rule flyout

[jughosta]

Kibana version: main (8.4)

Description of the problem including expected versus actual behavior:
Currently we allow to select a data view without a time field which results in a broken rule.

Steps to reproduce:

1. Have 2 data views: with time field and without one
2. Open a data view with a time field on Discover and press "Alerts" to open the flyout
3. Switch data view inside the flyout to the one without a time field
4. Notice that a rule is created but it shows a error on Rules and Connectors page

Expected:
A validation message that such rule can't be created based on a data view without a time field. Or we disable selecting such data views in the chooser component.

Originally posted in #134763 (review)

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[EricDavisX]

@jughosta this looks fixed to me, want to check it and close it out if so? Just making sure I hadn't misunderstood any details. Cheers.

[jughosta]

@EricDavisX The issue is still reproducible.

[EricDavisX]

Thanks, I must be looking at a different use case / work flow. Carry on, then. Cheers

[kertal]

Ideally we prevent the user from creating and adding such data view in the alert context. but, given we have no ad-hoc data views that also allow quick ad-hoc creation with auto-time field select (and selecting none if there's no matching field), it might not be that easy. So I think we should
a) Add a message / callout that the selected data view is not valid
b) Prevent saving such a rule, because it would not work, and just fail

[kertal]

Upgrading the issue to a bug, because it allows users to create invalid alert rule. The bugfix should prevent this by adding a message to the user, and preventing the saving of a data view without a time field. A potential follow up issue could be, to enhance the data view picker to don't allow creating data views without timefield if the component is configured that way. This should not change the way the data view picker works by default.