chore(stackable-operator): Demote kube_runtime::controller::Error::QueueError to warning

Note: This is because _everything_ was appearing as an error even when it was non-actionable. For example, when the crd maintainer updates the CA bundle on the CRD, the `metadata.resourceVersion changes` as expected. That leads to a controller error. Unfortunately there is currently no good way to discriminate error types. Something might need to be done upstream.

Author: NickLarsenNZ

crates/stackable-operator/src/logging/controller.rs

@@ -61,13 +61,26 @@ pub async fn report_controller_reconciled<K, ReconcileErr, QueueErr>(
                 "Reconciled object"
             );
         }
-        Err(error) => {
-            tracing::error!(
-                controller.name = controller_name,
-                error = error as &dyn std::error::Error,
-                "Failed to reconcile object",
-            );
-            publish_controller_error_as_k8s_event(recorder, error).await;
+        Err(controller_error) => {
+            match controller_error {
+                // Errors raised from queued stuff we will mark as _warning_.
+                // We can't easily discriminate any further.
+                controller::Error::QueueError(queue_error) => tracing::warn!(
+                    controller.name = controller_name,
+                    error = queue_error as &dyn std::error::Error,
+                    "Queued reconcile resulted in an error"
+                ),
+                // Assume others are _error_ level.
+                // NOTE (@NickLarsenNZ): Keeping the same error message as before,
+                // but am not sure if it is correct
+                _ => tracing::error!(
+                    controller.name = controller_name,
+                    error = controller_error as &dyn std::error::Error,
+                    "Failed to reconcile object"
+                ),
+            };
+
+            publish_controller_error_as_k8s_event(recorder, controller_error).await;
         }
     }
 }