[Rocket Replicator]Synchronization for configuration infos in the source and target Rmq Cluster.

**FEATURE REQUEST**

1. Please describe the feature you are requesting.
Synchronization for configuration infos in the source and target Rmq Cluster.The configuration infomation includes topicName,offeset,TopicPerm,QueueNum and some other Subscription data.

2. Provide any additional detail on your proposed use case for this feature.
Synchronization for configuration infos in the source and target Rmq Cluster.The configuration infomation includes topicName,offeset,TopicPerm,QueueNum and some other Subscription data.

3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
Synchronization for configuration infos in the source and target Rmq Cluster.The configuration infomation includes topicName,offeset,TopicPerm,QueueNum and some other Subscription data.

4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

- [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here,
- [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
- ...

Start by locating the Rocket Replicator entry point that handles synchronization between the source and target RMQ clusters. Define the configuration data that must be synchronized, including topicName, offset, TopicPerm, QueueNum, and subscription data. Done means these configuration values remain synchronized across both clusters; no files or tests are identified in the issue.

Written by the indexing model from the issue text.