Update pre-baked saved objects to use KQL instead of Lucene

[Bargs]

Since we default to KQL in 7.0 we should also use it as our default language in our pre-baked dashboards, visualizations, and saved searches. I'm starting a list here of things that should probably be updated:

• Sample data
• Beats dashboard (Dashboard for 7.0 need to be migrated to use KQL beats#10969)
• ML data recognizer modules (see [ML] Update data recognizer modules saved objects to use KQL instead of Lucene #32189)
• ML queries passed to dashboards and Discover in custom URLs (see [ML] Use KQL as the query language for custom URLs to Kibana pages #35469)

[elasticmachine]

Pinging @elastic/kibana-app

[Bargs]

cc @AlonaNadler @timroes @rayafratkina

[peteharverson]

The saved objects and custom URLs in the ML data recognizer modules should also be updated to use KQL rather than Lucene - have created a separate issue #32189 to cover the ML work.

[roncohen]

just making sure: pre-baked saved objects that are not upgraded to KQL will continue to work as expected in 7.0? or will the user experience suffer due the mismatch between the default and the saved object?

[Bargs]

@roncohen saved objects using lucene will continue to work fine. We just want to update pre-baked objects where possible so that when we say "KQL is the default now" users won't load up samples that are still lucene and be confused.

[peteharverson]

The saved objects and custom URLs in the ML data recognizer modules have now been converted to use KQL for 7.1 - done in #32189

[Bargs]

Thanks @peteharverson !

[timroes]

@Bargs It seems all items from the list are now done, can we close this?

[Bargs]

Appears so!