feat: adapted graceful shutdown docs

Author: dervoeti

docs/modules/trino/pages/usage-guide/operations/graceful-shutdown.adoc

@@ -80,10 +80,12 @@ spec:
 All queries that take less than the minimal graceful shutdown period of all roleGroups (`1` hour as a default) are guaranteed to not be disturbed by regular termination of Pods.
 They can obviously still fail when, for example, a Kubernetes node dies or gets rebooted before it is fully drained.
 
-Because of this, the operator automatically restricts the execution time of queries to the minimal graceful shutdown period of all roleGroups using the Trino configuration `query.max-execution-time=3600s`.
+Because of this, the operator automatically restricts the execution time of queries to the minimal graceful shutdown period of all roleGroups using the Trino configuration `query.max-execution-time=3600s` when xref:usage-guide/fault-tolerant-execution.adoc[fault tolerant execution] is not configured.
 This causes all queries that take longer than 1 hour to fail with the error message `Query failed: Query exceeded the maximum execution time limit of 3600s.00s`.
 
-In case you need to execute queries that take longer than the configured graceful shutdown period, you need to increase the `query.max-execution-time` property as follows:
+However, when xref:usage-guide/fault-tolerant-execution.adoc[fault tolerant execution] is enabled, the `query.max-execution-time` restriction is not applied since queries can be automatically retried in case of failures, allowing them to run indefinitely without being cancelled by worker restarts.
+
+In case you need to execute queries that take longer than the configured graceful shutdown period and do not want to configure fault tolerant execution, you can increase the `query.max-execution-time` property as follows:
 
 [source,yaml]
 ----
@@ -95,8 +97,6 @@ spec:
 ----
 
 Keep in mind, that queries taking longer than the graceful shutdown period are now subject to failure when a Trino worker gets shut down.
-Running into this issue can be circumvented by using https://trino.io/docs/current/admin/fault-tolerant-execution.html[Fault-tolerant execution], which is not supported natively yet.
-Until native support is added, you will have to use `configOverrides` to enable it.
 
 == Authorization requirements
 

rust/operator-binary/src/operations/graceful_shutdown.rs

@@ -27,16 +27,22 @@ pub fn graceful_shutdown_config_properties(
 ) -> BTreeMap<String, Option<String>> {
     match role {
         TrinoRole::Coordinator => {
-            let min_worker_graceful_shutdown_timeout = trino.min_worker_graceful_shutdown_timeout();
-            // We know that queries taking longer than the minimum gracefulShutdownTimeout are subject to failure.
-            // Read operator docs for reasoning.
-            BTreeMap::from([(
-                "query.max-execution-time".to_string(),
-                Some(format!(
-                    "{}s",
-                    min_worker_graceful_shutdown_timeout.as_secs()
-                )),
-            )])
+            // Only set query.max-execution-time if fault tolerant execution is not configured.
+            // With fault tolerant execution enabled, queries can be retried and run indefinitely.
+            if trino.spec.cluster_config.fault_tolerant_execution.is_none() {
+                let min_worker_graceful_shutdown_timeout = trino.min_worker_graceful_shutdown_timeout();
+                // We know that queries taking longer than the minimum gracefulShutdownTimeout are subject to failure.
+                // Read operator docs for reasoning.
+                BTreeMap::from([(
+                    "query.max-execution-time".to_string(),
+                    Some(format!(
+                        "{}s",
+                        min_worker_graceful_shutdown_timeout.as_secs()
+                    )),
+                )])
+            } else {
+                BTreeMap::new()
+            }
         }
         TrinoRole::Worker => BTreeMap::from([(
             "shutdown.grace-period".to_string(),