[Bug] Query fail when query timerMsg by real topic

### Before Creating the Bug Report

- [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions).

- [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate.

- [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

### Runtime platform environment

ubuntu

### RocketMQ version

develop

### JDK Version

_No response_

### Describe the Bug

This method performs special processing on the lmq and timer messages. It can obtain routing information based on the real/parent topic. However, when querying the timer message through the real topic, the cluster name will filter it, resulting in the inability to retrieve the message.

### Steps to Reproduce

query timerMsg by realtopic

### What Did You Expect to See?

query timer msg by realtopic

### What Did You See Instead?

null

### Additional Context

_No response_

No file or test is named; begin by locating the method that handles lmq and timer messages and the routing lookup used for a real or parent topic. Reproduce the real-topic timer-message query on Ubuntu against develop and trace why cluster-name filtering returns null. Done means the query returns the timer message for the real topic.

Written by the indexing model from the issue text.