[release/7.0] Avoid stream ID and client result ID collisions

[github-actions]

Backport of #46570 to release/7.0

/cc @BrennanConroy

Avoid stream ID and client result ID collisions

Description

The new Client Results features in 7.0 can cause a conflict with the Client Streaming feature in very specific cases. Specifically, when the client and server generate the same ID and then the client returns a result, which will complete the stream instead of completing the client result.

Fixes #46503

Customer Impact

In rare cases client to server streams can be completed accidentally and client results will end up timing out.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Narrow scope, combination of new and old feature, well understood issue.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[ghost]

Hi @github-actions[bot]. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[ghost]

Hi @github-actions[bot]. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[ghost]

Hi @github-actions[bot]. This PR was just approved to be included in the upcoming servicing release. Somebody from the @dotnet/aspnet-build team will get it merged when the branches are open. Until then, please make sure all the CI checks pass and the PR is reviewed.

[BrennanConroy]

@dotnet/aspnet-build any chance to merge before branch lock down?