[Bug] Fix potential NPE in EscapeBridge when topicPublishInfo is null

[Senrian]

Bug Description

In EscapeBridge.java, the methods asyncPutMessage() and asyncRemotePutMessageToSpecificQueue() call tryToFindTopicPublishInfo() but do not check for a null return value before dereferencing.

Issue: #10216

Location 1 - asyncPutMessage():

final TopicPublishInfo topicPublishInfo = this.brokerController.getTopicRouteInfoManager().tryToFindTopicPublishInfo(messageExt.getTopic());
final MessageQueue mqSelected = topicPublishInfo.selectOneMessageQueue(); // NPE if null

Location 2 - asyncRemotePutMessageToSpecificQueue():

final TopicPublishInfo topicPublishInfo = this.brokerController.getTopicRouteInfoManager().tryToFindTopicPublishInfo(messageExt.getTopic());
List<MessageQueue> mqs = topicPublishInfo.getMessageQueueList(); // NPE if null

Fix

Add null checks consistent with the existing pattern in putMessageToRemoteBroker():

if (null == topicPublishInfo || !topicPublishInfo.ok()) {
    LOG.warn("asyncPutMessage: no route info of topic {}...", ...);
    return CompletableFuture.completedFuture(new PutMessageResult(PutMessageStatus.PUT_TO_REMOTE_BROKER_FAIL, null, true));
}

This prevents NPE when a slave broker acting as master attempts to escape a message for a topic whose route information is not yet available.