Add time series related information to get data stream API

[martijnvg]

In case if a data stream is a time series data stream then include time series information.
This includes the continuous temporal ranges a time series data stream encapsulates.
This is computed based on combing the index.time_series.start_time and index.time_series.end_time
ranges of all backing indices of a time series data stream

Closes #83518

[elasticmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[martijnvg]

This change add time_series snippet to get data streams api response if a data stream is a time series data stream.
Example GET /_data_stream run:

{
    "data_streams": [
        {
            "name": "k8s",
            "timestamp_field": {
                "name": "@timestamp"
            },
            "indices": [
                {
                    "index_name": ".ds-k8s-2022.05.04-000001",
                    "index_uuid": "1C1g7at-RW6vz0kHEGx1ZA"
                },
                {
                    "index_name": ".ds-k8s-2022.05.04-000002",
                    "index_uuid": "nuh8WMrLROmrzkRPb1fu1w"
                }
            ],
            "generation": 2,
            "status": "GREEN",
            "template": "k8s-template",
            "ilm_policy": "7-days-1gb-rollover",
            "hidden": false,
            "system": false,
            "allow_custom_routing": false,
            "replicated": false,
            "time_series": {
                "temporal_ranges": [
                    {
                        "start": "2022-05-04T12:14:53.000Z",
                        "end": "2022-05-04T12:43:26.000Z"
                    }
                ]
            }
        }
    ]
}

[elasticmachine]

Pinging @elastic/clients-team (Team:Clients)

[sethmlarson]

LGTM from an API perspective

[martijnvg]

LGTM from an API perspective

Thanks @sethmlarson for reviewing!

[nik9000]

Could you fail if the indices aren't in time series order? Or warn or something? Just out of paranoia.

[nik9000]

Or sort them by start time.

[martijnvg]

The indices are in order in which they are created. (new data stream, rollover, rollover again -> 3 backing indices that are in order). So the start / end times should be in order.

I will add an assertion and ensure a warning log gets printed (if this ever should occur in production). Which I don't think should be the case.

[martijnvg]

@elasticmachine update branch