[BUG] KoP cannot start with preciseTopicPublishRateLimiterEnable

[BewareMyPower]

Describe the bug
apache/pulsar#7078 introduced the precise topic publish rate limiter, but if it was enabled in KoP, KoP would fail to start.

To Reproduce
Append following configurations to conf/standalone.conf:

messagingProtocols=kafka
kafkaListeners=PLAINTEXT://127.0.0.1:9092
brokerEntryMetadataInterceptors=org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor
entryFormat=kafka
allowAutoTopicCreationType=partitioned
brokerDeleteInactiveTopicsEnabled=false
preciseTopicPublishRateLimiterEnable=true

Then start standalone by bin/pulsar standalone.

The 6650 and 8080 ports were listened on, which means the broker service and web service succeeded to start. But the 9092 port was never listened on, which means KoP didn't start.

After I removed the preciseTopicPublishRateLimiterEnable=true config and restart, it worked well.

Expected behavior
KoP should start successfully with preciseTopicPublishRateLimiterEnable=true.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
There're a lot of logs like:

16:41:52.822 [pulsar-timer-78-1] INFO  org.apache.pulsar.client.impl.ProducerImpl - [public/__kafka/__consumer_offsets-partition-42] [standalone-1-7] Message send timed out. Failing 1 messages
... (each partition of __consumer_offsets)
16:41:52.850 [pulsar-timer-78-1] INFO  org.apache.pulsar.client.impl.ProducerImpl - [public/__kafka/__consumer_offsets-partition-9] [standalone-1-40] Message send timed out. Failing 1 messages

It could also be reproduced in unit tests, just add

kafkaConfig.setPreciseTopicPublishRateLimiterEnable(true);

to KopProtocolHandlerTestBase#resetConfig and run any test.

[BewareMyPower]

It's fixed by apache/pulsar#11446 that will be included in Pulsar 2.8.1.