[Star tree] Adding date field rounding support in star tree

[bharath-techie]

Description

User can give up to three calendar_intervals as part of Date_Dimension as part of star tree mapping. We will round off the value in date field as per the interval. Both nano and millis resolution are rounded off.

Anything greater than or equal to Hour interval will only work for UTC timezone and 00:00 offset.

We will add support for timezones and offsets later. #15266

        "composite": {
            "startree1: {
                "type": "star_tree",
                "config": {
                    "ordered_dimensions": [
                        {
                            "name": "size"
                        }
                    ],
                    "date_dimension": {
                        "name": "date",
                        "calendar_intervals": [
                            "minute",
                            "hour",
                             "day"
                        ]
                    },
                    "metrics": [
                        {
                            "name": "size",
                            "stats": [
                                "sum",
                                "count"
                            ]
                        }
                    ]
                }
            }
        }

User can specify date dimension as above with defaults being 'minute' and 'half an hour'. The date field ( both milliseconds and nanoseconds resolution ) will get rounded off to the associated calendar interval.

Apart from date histogram calendar intervals,
User can provide quarter of hour / half an hour as part of mapping .

15m (or) quarter-hour
30m (or) half-hour

This is done to handle all timezones.
15m interval will handle all timezones and 30m interval will handle 99% of timezones bar the ones which has :45 minute part as part of timezone.

Related Issues

Resolves #15265

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for 5fdce71: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 23e600a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 6fbaf1b: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 93760bc: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❕ Gradle check result for d34a36f: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[github-actions]

❌ Gradle check result for 309f539: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for d9e7852: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 8215865: SUCCESS