To refactor KafkaSink to use more workers for message production.

[asddongmen]

Is your feature request related to a problem?

To ensure all data from a table are sent sequentially downstream to Kafka, the KafkaSink uses only one worker to produce messages of a changefeed (in a processor).
This means that only one TCP connection is established between CDC and the Kafka server. Therefore, in case of high network latency, the throughput of KafkaSink can significantly deteriorate. (See #10775)

Describe the feature you'd like

• To refactor KafkaSink to use more workers for message production of different table, which should be helpful in high network latency case.

Describe alternatives you've considered

No response

Teachability, Documentation, Adoption, Migration Strategy

No response