drainer: fix kafka message limit problem (#1039)

[ti-chi-bot]

This is an automated cherry-pick of #1039

What problem does this PR solve?

When we use kafka as downstream, the transaction size exceed 1G can't to transport to downstream.

What is changed and how it works?

1. Set grpc message limit to IntMax instead of max.Int32.
2. Add configuration max-message-size in drainer's config.

Check List

Tests

• Unit test
• Integration test

Code changes

• Has exported variable/fields change

Related changes

• Need to cherry-pick to the release branch
• Need to be included in the release note

Release note

• Set grpc message limit to IntMax instead of max.Int32. Add configuration max-message-size in drainer's config.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• glorv
• lichunzhu

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.

[lichunzhu]

/merge

[ti-chi-bot]

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

Commit hash: a17a8e6

[ti-chi-bot]

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.