Allow configuring per index query timespan limits

[LeeDr]

Describe the feature: Add an optional setting on index patterns in Kibana that lets you configure a limit on the timespan used for queries on that index.

Describe a specific use case for the feature:
A user at an AMA booth approached me with this problem they were having. They have 2 types of indices. One type has small docs and/or sparse docs over time, and they would often query large timespans on these indices in Discover. The other type of index has very large docs and/or a high frequency of docs over time.
When they switch index from the small index type to the large index type in Discover while they had a large timespan selected in the time picker, then Discover is going to run the query against that large timespan with negative consequences.

I think this optional setting would have choices similar to the timepicker quick choices, 1 hour, 4 hours, 12 hours, 23 hours, week, month, N months... At the max end, you just don't select the option which means unlimited timespan.

[LeeDr]

@jimgoodwin also suggested allowing to select fields to exclude from being visible in Kibana (for perf reasons, not security). This could be a separate enhancement request.

[alexfrancoeur]

Linking to a similar concept, but not an index level. Instead, as an advanced setting per space: #82414

[sudonima]

this is important for our company! please add this feature!

[elasticmachine]

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

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.