Allow specifying of default values in Input Controls

[timroes]

It would be nice if a user (mostly affecting users with more data, that will hit the terminate_after we send for gathering the initial top x terms), could specify a default list of values that should be shown. If that list would be specified there would be no initial request to gather the top x terms, but instead the list would be shown and only once the user starts typing the requests would be made to fetch data matching that quert.

[elasticmachine]

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

[Heenawter]

Changing this to impact:low because the ignore_timeout setting in the new controls acts as a workaround for ensuring that even users with exceptionally large data will see some results. That being said, if load times are an issue that they want to overcome, I think specifying a list of defaults is an option for this - just not sure how widely impactful this feature would be, especially once #140112 is implemented.

Keeping this open for now, as something to consider. But I think if we decide to go the pre-filtering route, this issue should be closed alongside the previous issue once this capability is added.

[ThomThomson]

Closing this because the point of the new Controls is to fetch options from the field, and if an author had the option to type out the available options, that could result in data changes not being picked up, selections resulting in no data and the chaining system not working.