test(integration-tests): fix TopicTracingIT flaky test (kroxylicious#3859)

Add wait for topicB metadata propagation before deletion to prevent
UnknownTopicIdException. The test was creating topicB with the 'setup'
admin client then immediately deleting it with a different 'admin'
client without waiting for metadata to propagate between clients.

Fixes kroxylicious#3858

Assisted-by: Claude Sonnet 4.5 <noreply@anthropic.com>

Signed-off-by: Keith Wall <kwall@apache.org>

Author: k-wall

kroxylicious-integration-tests/src/test/java/io/kroxylicious/it/filter/authorization/TopicTracingIT.java

@@ -155,6 +155,7 @@ public void run(ClientFactory clientFactory) {
                     admin.describeConfigs(ConfigResource.Type.TOPIC, topicA);
                     admin.alterConfigs(ConfigResource.Type.TOPIC, topicA, new ConfigEntry(TopicConfig.COMPRESSION_TYPE_CONFIG, "zstd"));
                     var topicBId = setup.createTopic(topicB).value();
+                    Awaitility.waitAtMost(10, TimeUnit.SECONDS).until(() -> ClusterPrepUtils.allTopicPartitionsHaveALeader(setup.admin(), List.of(TOPIC_B)));
 
                     admin.deleteTopic(topicBId);
                 }