fix: remove execution retries from DROP STREAM DELETE TOPIC

Retrying a DROP STREAM DELETE TOPIC commands are delayed when
retrying the failed command. This is not necessary when the
TopicDeletionDisabledException is False, and even for any
other error. Users can retry the command manually if it fails.

ksql-engine/src/main/java/io/confluent/ksql/topic/TopicDeleteInjector.java

@@ -30,8 +30,6 @@
 import io.confluent.ksql.services.ServiceContext;
 import io.confluent.ksql.statement.ConfiguredStatement;
 import io.confluent.ksql.statement.Injector;
-import io.confluent.ksql.util.ExecutorUtil;
-import io.confluent.ksql.util.ExecutorUtil.RetryBehaviour;
 import io.confluent.ksql.util.KsqlConstants;
 import io.confluent.ksql.util.KsqlException;
 import java.util.Objects;
@@ -93,9 +91,7 @@ public <T extends Statement> ConfiguredStatement<T> inject(
 
     if (source != null) {
       try {
-        ExecutorUtil.executeWithRetries(
-            () -> topicClient.deleteTopics(ImmutableList.of(source.getKafkaTopicName())),
-            RetryBehaviour.ALWAYS);
+        topicClient.deleteTopics(ImmutableList.of(source.getKafkaTopicName()));
       } catch (Exception e) {
         throw new KsqlException("Could not delete the corresponding kafka topic: "
             + source.getKafkaTopicName(), e);