[BUG] Invalid handling of time filter in PPL

[Smjert]

Describe the bug

Invalid handling of time filter in PPL

To Reproduce

Steps to reproduce the behavior:

1. Login anonymous in the future playground.
2. Select the OTEL demo environment.
3. Select Discover from the menu on the left hand side
4. In the data source selection dropdown, type ecomm, then select the first item opensearch*ecomm*
5. Using PPL query mode, set the time filter to absolute mode starting at Oct 20, 2024 @ 00:00:00.00 and ending at Oct 20, 2024 @23:00:00.00 then run source = opensearch*ecomm*,
   • Results having timestamps on both Oct 19 and Oct 20 are shown. As no timezone information is presented the assumption is that it is at least the same timezone and thus incorrect.

Expected behavior

• Step 5: Results are shown in a list of entries with Time and _source, all within the selected timeframe.

OpenSearch Version

2.18

Dashboards Version

2.18

Plugins

Alerting, anomaly-detection, asynchronous-search, cross-cluster-replication, custom-codecs, flow-framework, geospatial, index-management, job-scheduler, knn, ml, neural-search, notifications, notifications-core, observability, performance-analyzer, reports-scheduler, security, security-analytics, skills, sql, system-templates, query-insights

Screenshots

N/A

Host/Environment:

• OS: macOS
• Browser and version Google Chrome, version 131.0.6778.205

Additional context

N/A