tso: fix tso proxy error propagation (#9219)

[ti-chi-bot]

This is an automated cherry-pick of #9219

What problem does this PR solve?

Issue Number: Close #9188

What is changed and how does it work?

The change fixes the problems outlined in #9188 (comment)

• Don't block client stream on receiving next request and allow to return error from proxy
• Allow to return proxy error to all clients served by the proxy error
• Don't cancel proxy stream after original client stream is closed

Tested using the same way as reported in the issue and observe subsecond impact only now:

[ 67s ] thds: 64 tps: 2007.63 qps: 2007.63 (r/w/o: 0.00/2007.63/0.00) lat (ms,95%): 116.80 err/s: 0.00 reconn/s: 0.00
[ 68s ] thds: 64 tps: 1962.21 qps: 1962.21 (r/w/o: 0.00/1962.21/0.00) lat (ms,95%): 121.08 err/s: 0.00 reconn/s: 0.00
[ 69s ] thds: 64 tps: 1984.16 qps: 1984.16 (r/w/o: 0.00/1984.16/0.00) lat (ms,95%): 116.80 err/s: 0.00 reconn/s: 0.00
[ 70s ] thds: 64 tps: 504.00 qps: 504.00 (r/w/o: 0.00/504.00/0.00) lat (ms,95%): 646.19 err/s: 0.00 reconn/s: 0.00
[ 71s ] thds: 64 tps: 1607.99 qps: 1607.99 (r/w/o: 0.00/1607.99/0.00) lat (ms,95%): 125.52 err/s: 0.00 reconn/s: 0.00
[ 72s ] thds: 64 tps: 2010.98 qps: 2010.98 (r/w/o: 0.00/2010.98/0.00) lat (ms,95%): 116.80 err/s: 0.00 reconn/s: 0.00
[ 73s ] thds: 64 tps: 1965.68 qps: 1965.68 (r/w/o: 0.00/1965.68/0.00) lat (ms,95%): 123.28 err/s: 0.00 reconn/s: 0.00

Check List

Tests

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

Code changes

• Has the configuration change
• Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tiup:
• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign overvenus for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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 kubernetes-sigs/prow repository.

[ti-chi-bot]

@ti-chi-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci/build	53dc2c9	link	true	/test build

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.