[Bug] sometimes it may cause the ConsumeQueueTable info recreated in memory for not exist topic

[absolute8511]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

All

RocketMQ version

All

JDK Version

All

Describe the Bug

some read only command may cause the non-exist topic consume queue info recreate in consume queue store. It is caused by using findConsumeQueue in some read only functions and the findConsumeQueue will create the ConsumeQueue info if not exist. We should not use it in read only functions to avoid create not exist topic consume queue by accident.

Steps to Reproduce

1. consume the topic with long poll and waiting for no message
2. delete topic
3. the long poll will wakeup and recreate the consume queue info in ConsumeQueueTable
4. send GET_EARLIEST_MSG_STORETIME command for non-exist topic can also cause ConsumeQueueTable insert non-exist topic info.

What Did You Expect to See?

no more consume queue info in ConsumeQueueTable after the topic deleted

What Did You See Instead?

consume queue recreated in ConsumeQueueTable after the topic deleted

Additional Context

No response