[WIP] Surface information about indices and index patterns when creating a new index pattern.

[cjcenizal]

Addresses #10438 and #5053

Here's the flow I'm going to shoot for:

Replaces #11748

[snide]

Pretty close. Glad you're thinking about making one of these. Couple notes.

1. You don't need the language on most of these. Most of this stuff is normal patterns people are used to. If you want to illustrate that it's a partial match it's better to highlight part of the word logstash.
2. Likely want a placeholder or help text to let them know they can use *
   • When * is used nothing should be selectable. You'll want to visually separate the matches from selections somehow. The only selectable item is the "will match against all...".
3. Since they can't just hit enter on "log" when it's a partial match, you should always have something in the select state (default would be the first item matched). Essentially this means your second pane can be dropped, it'll always be the third pane in some form.
4. Looking at the way they've been doing this with the watcher PR, you'll need an empty state (no results) and a loading state. Usual place for the loader is to replace the caret icon with a small spinner while it "loads".
5. Can people select more than one? If so you'll need pills.
6. Search is going to be a ton more specific than tabs. Simply putting the (type) next to the result in a mixed list is enough and will be much faster for the user.

You might want to check out some of the patterns established in K7 for this kind of stuff. It has exception examples for what to do when things get too long...etc.

[cjcenizal]

Closing in favor of #12530