fix: query execution at the time of hottier eviction (#1797)

* fix: query execution at the time of hottier eviction

query takes a guard if time range matches hottier eviction flow
skips the hottier sync cycle so query can be served from hottier

add check to skip stream related tasks for suspended tenants like -
- hottier sync
- retention task

* serve query from object store if query_guard fails

* reuse in enterprise

* reconciliation and failed-download cleanup to respect query pins

* coderabbit comments and deepsource fix

* fix issue with unguarded queries

Author: nikhilsinhaparseable

src/alerts/alerts_utils.rs

@@ -40,6 +40,7 @@ use crate::{
     option::Mode,
     parseable::PARSEABLE,
     query::{QUERY_SESSION, execute, resolve_stream_names},
+    tenants::TENANT_METADATA,
     utils::time::TimeRange,
 };
 
@@ -57,6 +58,14 @@ use super::{ALERTS, AlertError, AlertOperator, AlertState};
 ///
 /// check whether notification needs to be triggered or not
 pub async fn evaluate_alert(alert: &dyn AlertTrait) -> Result<(), AlertError> {
+    if alert
+        .get_tenant_id()
+        .as_deref()
+        .is_some_and(|tenant| TENANT_METADATA.is_workspace_suspended(tenant))
+    {
+        return Ok(());
+    }
+
     trace!("RUNNING EVAL TASK FOR- {alert:?}");
 
     let message = alert.eval_alert().await?;