[Feature] In pull mode, provide PushConsumer with precise control of consumption rate

[cserwen]

Is Your Feature Request Related to a Problem?

If we set clientRebalance as false, we can noly control consumption rate by following configurations:

consumeThreadMin
consumeThreadMax

In some scenarios, even a single thread may exceed the consumption rate that the business can accept. And it is difficult to calculate how many threads should be set based on the consumption rate

Generally, developers use RateLimiter to control the rate in the consumer listener, but this can easily lead to consume-timeouts. It is best to provide this function within the SDK.

Describe the Solution You'd Like

Developers can set following configurations to control consumption rate:

enableConsumeRateLimit=true
// 10 qps/s for single consumer
consumptionRate=10

Describe Alternatives You've Considered

Use RateLimiter to control rate in the messageListener

RateLimiter rateLimiter = RateLimiter.create(10);
consumer.registerMessageListener(new MessageListenerConcurrently() {
    @Override
    public ConsumeConcurrentlyStatus consumeMessage(List<MessageExt> msgs, ConsumeConcurrentlyContext context) {
        rateLimiter.acquire();
        System.out.printf("%s Receive New Messages: %s %n", Thread.currentThread().getName(), msgs);
        return ConsumeConcurrentlyStatus.CONSUME_SUCCESS;
    }
});

Additional Context