Kibana support for Date_Range field types in Date Histograms and for Timepicker

[foreman3]

Describe the feature:
Elasticsearch supports date_range types, but Kibana identifies these types as unknown. It would be good if these fields could be used in Kibana as the Time Filter field for an index, and also for Date Histograms.

Using a date_range field as the field for a time filter should also allow the user to specify the date range relation parameter (WITHIN, CONTAINS, INTERSECTS) so users can specify the required behavior for each visualization or dashboard for that index

Date_Range fields should also support Date Histograms. Elasticsearch has support for this aggregation as an open item (issue #34644), but Kibana should support it when ready.

Describe a specific use case for the feature:

Much of our data has a "Session"-like nature, with a start and end date. Currently, we write a record once when the session begins with the correct start date, and an end date of "2099". When the session ends, we update the records with the correct end date. Right now we can do some interesting things in Kibana:

We can use the Start Date as the Time Filter field, and get metrics about session start started in a given range.
Or we don't use any Time Filter, and instead set a Dashboard filter where "end date is > 2099", which let's us see metrics about all open sessions.
But our end user would like to be able to look at a given time range, say month or day and see metrics about the sessions that were active during that period, such as "top 10 counties" with active sessions during that period. Right now that's possible by adding 2 filters manually to the dashboard ("start date < date of interest" and "end date > date of interest"). But this isn't very intuitive. It would be great if the time filter could be used for this.

Supporting Date Histograms then could be used to get the Counts, or Averages, or Top Hits by bucket, letting us see stuff like the Top Country for each month for the last year, etc.

[elasticmachine]

Pinging @elastic/kibana-app

[timroes]

Related to #12751 Will leave this open nevertheless, since it has a pretty decent description.

[kananmammadli]

I would add one more use case for the same data.
it is to match active session count mapped on a time series to see the dynamics of open sessions. It will let end users to see for example active session count per second.

[ppisljar]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.