[Feature]Add the local storage function for historical offset

[gosonzhang]

Description

Currently, TubeMQ saves the offset of the consumption group through ZooKeeper. When the operation and maintenance personnel want to view the offset of a consumption group, they need to periodically read the offset from the Broker or ZooKeeper and save it.

In response to this problem, we consider constructing a system topic through Broker, and regularly save the Offset of the consumption group consumed online to the topic. Someone that wants to know the consumption history only needs to consume the topic to obtain the consumption offset history of the corresponding group, which is somewhat similar to Kafka the historical Offset saving scheme. Considering the subsequent functional expansion of TubeMQ, ZooKeeper still retains the current offset of the consumer group.

The issue is tracked and managed for this feature.

• [x] #2232
• [x] #2247
• [x] #2254
• [ ] #2291
• [ ] #2292

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.