sink(ticdc): limit encoder-concurrency to avoid crash

[wk989898]

What problem does this PR solve?

Issue Number: close #11773

What is changed and how it works?

As title. The maximum value is CPU count * 10

Check List

Tests

• Unit test
• Integration test

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

`None`.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 55.1680%. Comparing base (ea35677) to head (5961029).

Additional details and impacted files

Components	Coverage Δ
cdc	59.6172% <0.0000%> (+0.0328%)	⬆️
dm	50.0384% <ø> (+0.0019%)	⬆️
engine	53.2054% <ø> (-0.0339%)	⬇️

Flag	Coverage Δ
unit	55.1680% <0.0000%> (+0.0126%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

@@               Coverage Diff                @@
##             master     #11775        +/-   ##
================================================
+ Coverage   55.1554%   55.1680%   +0.0126%     
================================================
  Files          1002       1002                
  Lines        137399     137402         +3     
================================================
+ Hits          75783      75802        +19     
+ Misses        56073      56059        -14     
+ Partials       5543       5541         -2     

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[wk989898]

/retest

[wk989898]

/retest

[wk989898]

/retest

[wk989898]

/run-check-issue-triage-complete

[3AceShowHand]

/retest

[wk989898]

/cherry-pick release-8.5

[ti-chi-bot]

@wk989898: once the present PR merges, I will cherry-pick it on top of release-8.5 in the new PR and assign it to you.

In response to this:

/cherry-pick release-8.5

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.

[ti-chi-bot]

@wk989898: new pull request created to branch release-8.5: #11792.

In response to this:

/cherry-pick release-8.5

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.

[ti-chi-bot]

@wk989898: cannot checkout release-8.1 release-7.5 release-7.1 release-6.5 release-6.1: error checking out release-8.1 release-7.5 release-7.1 release-6.5 release-6.1: exit status 1. output: error: pathspec 'release-8.1 release-7.5 release-7.1 release-6.5 release-6.1' did not match any file(s) known to git

In response to this:

/cherry-pick release-8.1 release-7.5 release-7.1 release-6.5 release-6.1

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.

[ti-chi-bot]

@wk989898: cannot checkout release-8.1, release-7.5, release-7.1, release-6.5, release-6.1: error checking out release-8.1, release-7.5, release-7.1, release-6.5, release-6.1: exit status 1. output: error: pathspec 'release-8.1, release-7.5, release-7.1, release-6.5, release-6.1' did not match any file(s) known to git

In response to this:

/cherry-pick release-8.1, release-7.5, release-7.1, release-6.5, release-6.1

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.

[wk989898]

/cherry-pick release-8.1

[ti-chi-bot]

@wk989898: new pull request created to branch release-8.1: #11795.

In response to this:

/cherry-pick release-8.1

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.

[wk989898]

/cherry-pick release-7.5

[wk989898]

/cherry-pick release-7.1

[wk989898]

/cherry-pick release-6.5

[wk989898]

/cherry-pick release-6.1

[ti-chi-bot]

@wk989898: new pull request created to branch release-7.5: #11796.

In response to this:

/cherry-pick release-7.5

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.

[ti-chi-bot]

@wk989898: new pull request created to branch release-7.1: #11797.

In response to this:

/cherry-pick release-7.1

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.

[ti-chi-bot]

@wk989898: new pull request created to branch release-6.5: #11798.

In response to this:

/cherry-pick release-6.5

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.

[ti-chi-bot]

@wk989898: new pull request created to branch release-6.1: #11799.

In response to this:

/cherry-pick release-6.1

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.