[Discover] Show a fallback empty message when no results are found

[jughosta]

Closes #126594

Summary

Next to "No results match your search criteria" title in Discover UI, we show a helpful suggestion on what can be adjusted in the search criteria (time range, search query or filters) to still find some results. This PR adds a fallback message which otherwise suggests to make sure that selected data view points to available indices with documents.

During testing, please check these cases:

• with a data view without a time field
• with a data view for an index without documents
• with a data view for a deleted index

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

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

[jughosta]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 3768a6b
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
discover	433	438	+5

Async chunks

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

id	before	after	diff
discover	383.5KB	384.0KB	+562.0B

History

• 💚 Build #34591 succeeded 85fb7bf
• 💔 Build #34519 failed 01d6c2f

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

[kertal]

Code LGTM, congrats 🎉 ! That's a great debut in the Kibana code base. This PR fixes the issue and makes the code much clearer and better to read! Thx a lot. Works as expected in Safari, Firefox, Chrome, locally tested with a M1 Mac.

And due to the useful description you've added, I also found an issue with the existing way we handle errors. So, I deleted an index I've created for showing the new message. In this case there was an error toast displayed, that's easy to miss. I think the error should be displayed via the no_results component. It's nothing severe, but I think we should fix it in a follow up PR. Here's an example for that, deleted the index, and the toast is easy to miss:

Kapture.2022-03-30.at.17.32.56.mp4