kvclient(ticdc): close the grpc client after all goroutine exited to prevent data race and panic

[3AceShowHand]

What problem does this PR solve?

Issue Number: close #10799

What is changed and how it works?

• use errgroup context to control grpc stream, to make it can be canceld.
• do not set the grpc stream to nil after CloseSend

Check List

Tests

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

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

Merging #10865 (207491d) into master (db60e9e) will decrease coverage by 0.1204%.
Report is 3 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

Components	Coverage Δ
cdc	61.6824% <100.0000%> (-0.1951%)	⬇️
dm	51.3141% <ø> (+0.0646%)	⬆️
engine	63.4585% <ø> (+0.0635%)	⬆️

Flag	Coverage Δ
unit	57.4355% <100.0000%> (-0.1204%)	⬇️

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

@@               Coverage Diff                @@
##             master     #10865        +/-   ##
================================================
- Coverage   57.5558%   57.4355%   -0.1204%     
================================================
  Files           853        850         -3     
  Lines        126974     125257      -1717     
================================================
- Hits          73081      71942      -1139     
+ Misses        48454      47931       -523     
+ Partials       5439       5384        -55     

[3AceShowHand]

/test all

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asddongmen, CharlesCheung96

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [CharlesCheung96,asddongmen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-02 03:13:16.090268028 +0000 UTC m=+327257.617808576: ☑️ agreed by CharlesCheung96.
• 2024-04-02 06:57:30.999477598 +0000 UTC m=+340712.527018145: ☑️ agreed by asddongmen.

[3AceShowHand]

/retest

[3AceShowHand]

/test cdc-integration-storage-test

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #10906.

[3AceShowHand]

/cherry-pick release-7.5

[ti-chi-bot]

@3AceShowHand: new pull request could not be created: failed to create pull request against pingcap/tiflow#release-7.5 from head ti-chi-bot:cherry-pick-10865-to-release-7.5: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-10865-to-release-7.5."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

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.