Improve doGet debug log when status is unexpected

Include okStatusCodes in the debug message when a GET response has a
status code not in the allowed set, per review feedback.

Signed-off-by: Parameshwaran Krishnasamy <Parameshwaran.K@ibm.com>

Author: Paramesh324

cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/assembly/KafkaConnectApiImpl.java

@@ -131,7 +131,8 @@ private <T> CompletableFuture<T> doGet(Reconciliation reconciliation, String hos
                         LOGGER.debugCr(reconciliation, "Got {} response to GET request to {}: {}", statusCode, path, json.asText());
                         return CompletableFuture.completedFuture(OBJECT_MAPPER.convertValue(json, type));
                     } else {
-                        LOGGER.debugCr(reconciliation, "Got {} response to GET request to {}", statusCode, path);
+                        LOGGER.debugCr(reconciliation, "Got unexpected {} response to GET request to {}. Ok status codes: {}",
+                                statusCode, path, okStatusCodes);
                         String message;
                         if (statusCode >= 200 && statusCode < 300) {
                             // Unlisted 2xx: poll may get 200 before 404 after delete.