add support of wildcard when selecting visualize

[TomonoriSoejima]

Describe the feature:

Describe a specific use case for the feature:

It would be handy if we support wildcards such as * when selecting visualize to add to the dashboard.

Adding a screenshot that shows that currently * is not treated as a wildcard.

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[flash1293]

Pinging both core and kibana app for this because I'm not sure where to resolve it. I stumbled over the very same thing just today, and I agree that this would be super helpful. We probably should implement it in all the places.

I came across this in the context of the field list in Lens/Discover

It would be super helpful to be able to type graph*numLinks here as well.

[pgayvallet]

Yea, * wildcard query are not supported by ES's SQS, which is what we're using for the SO find API (the * wildcard is used for prefix search in SQS)

This would require adding an additional (or replacement) wildcard query to the request we're forging when searching for SOs.

This will probably have to wait for SO v2, where we're planning to allow our API consumers to directly provide an raw ES query when searching for SOs

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[ThomThomson]

Removing the presentation team label and adding the shared UX label as this has more to do with Content Management.