SLO support | elastic search database

<!-- Please only use this template for submitting feature requests --> Why is this needed: Currently, Grafana’s SLO (Service Level Objective) features and panels primarily rely on data sources like Prometheus or Loki for error rate and latency metrics. However, many users and organizations store operational metrics, logs, and performance indicators in Elasticsearch. Without native SLO support for Elasticsearch, users must rely on manual queries, complex transformations, or external tools to calculate SLOs, SLIs, and error budgets. This limits usability and prevents unified SLO visualization in Grafana when Elasticsearch is a primary data source. What would you like to be added: Add native SLO support for Elasticsearch data source, enabling: Direct configuration of SLOs using Elasticsearch queries (e.g., success/failure counts, latency thresholds). Built-in functions or query templates for calculating SLIs and error budgets. Compatibility with Grafana’s existing SLO dashboard panels and alerting mechanisms. Support for time-based rollups and aggregations from Elasticsearch indices. Who is this feature for? Teams using Elasticsearch as their main observability or metrics backend. Organizations seeking to visualize, track, and alert on SLOs within Grafana without maintaining multiple data sources. DevOps and SRE teams that already rely on Elasticsearch for service performance data and want to integrate SLO monitoring seamlessly.