sink: fix kafka max message size inaccurate issue. (#3002)

[ti-chi-bot]

This is an automated cherry-pick of #3002

What problem does this PR solve?

try to close #2962

What is changed and how it works?

• When calculating the length of encoded MQMessage, also consider the maximumRecordOverhead, which was introduced by the sarama client.
• Ignoring max-message-size at the producer level, default to 512m. max-message-size only works for the encoder.
• Change log level to Debug when AppendRowChangedEvent in json encoder.

Check List

Tests

• Unit test
• Manual test (add detailed scripts or steps below)

Code changes
Side effects

Related changes

Release note

fix kafka sink can not send message due to constraint by `max-message-size` option.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[3AceShowHand]

/run-integration-tests
/run-kafka-tests

[3AceShowHand]

/run-integration-tests

[amyangfei]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: b0d7ef5