[Enhancement] Implement paged retrieval of topic and subscription group information

[ltamber]

Before Creating the Enhancement Request

• [x] I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

By introducing sequence-based pagination, you can safely handle large metadata sets like Topic and SubscriptionGroup configurations, ensuring compatibility with Netty’s frame limits and improving robustness across environments.

Motivation

When retrieving topic or subscription group information via getAllTopicConfig and getAllSubscriptionGroup, if the number of topics or groups is too large, the serialized data may exceed Netty's maxFrameLength, leading to invocation failures.

Describe the Solution You'd Like

Modify the request logic so that clients can specify:

• A starting sequence number (topicSeq or groupSeq)
• Maximum number of items to return per request (maxTopicNum or maxGroupNum)

This allows the client to fetch data in smaller, manageable chunks.

Describe Alternatives You've Considered

none

Additional Context

No response