Fix topic deletion issue in master-slave clusters

Issue: Topics cannot be permanently deleted in master-slave RocketMQ clusters
because slave brokers incorrectly delete all topics during synchronization.

Root Cause: In SlaveSynchronize.java, the deleteTopicConfig() call was placed
outside the conditional check, causing ALL topics to be deleted from slaves
during sync, not just the ones missing from master's config.

Fix: Move deleteTopicConfig() and deleteSubscriptionGroupConfig() calls inside
the conditional blocks so they only execute for topics/subscription groups that
should actually be deleted.

This addresses GitHub issue #10030 and is related to issue #9984.

Changes:
- syncTopicConfig(): Move topicConfigManager.deleteTopicConfig() inside if block
- syncSubscriptionGroupConfig(): Move subscriptionGroupManager.deleteSubscriptionGroupConfig() inside if block

Author: FaisalMisbah23

broker/src/main/java/org/apache/rocketmq/broker/slave/SlaveSynchronize.java

@@ -94,8 +94,8 @@ private void syncTopicConfig() {
                         Map.Entry<String, TopicConfig> entry = iterator.next();
                         if (!newTopicConfigTable.containsKey(entry.getKey())) {
                             iterator.remove();
+                            topicConfigManager.deleteTopicConfig(entry.getKey());
                         }
-                        topicConfigManager.deleteTopicConfig(entry.getKey());
                     }
 
                     //update
@@ -189,8 +189,8 @@ private void syncSubscriptionGroupConfig() {
                         Map.Entry<String, SubscriptionGroupConfig> configEntry = iterator.next();
                         if (!newSubscriptionGroupTable.containsKey(configEntry.getKey())) {
                             iterator.remove();
+                            subscriptionGroupManager.deleteSubscriptionGroupConfig(configEntry.getKey());
                         }
-                        subscriptionGroupManager.deleteSubscriptionGroupConfig(configEntry.getKey());
                     }
                     // update
                     newSubscriptionGroupTable.values().forEach(subscriptionGroupManager::putSubscriptionGroupConfig);