[rocketmq-replicator] Realize consumption offset synchronization

1. Please describe the feature you are requesting.
- Provide MetaSinkTask, call MetaSinkTask in WorkerDirectTask to write data directly to the target cluster.
- In MetaSinkTask, the updateConsumeOffset method will be called to update the target cluster consumeOffset.

2. Provide any additional detail on your proposed use case for this feature.
- #824

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?
- should-have

4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
- Maintain BrokerName mapping（ISSUE has not been submitted）
- Maintain the ConsumeOffset deviation between the target cluster and the source cluster（ISSUE has not been submitted）

Start by reading the rocketmq-replicator implementation around MetaSinkTask and WorkerDirectTask, then review issue #824 for context. Trace how updateConsumeOffset is currently expected to update the target cluster and determine how BrokerName mapping and ConsumeOffset deviation handling fit the requested synchronization. Done means the target cluster's consumption offset is updated through MetaSinkTask when invoked by WorkerDirectTask.

Written by the indexing model from the issue text.