[2.1] Port "Do not expand stacktraces when completion exception is rethrown multiple times"

[pakrym]

Ports #31375 and #31685
Fixes #31388

2.1 template

Description

Multiple calls to ReadAsync on the faulted pipe would produce exceptions with ever-increasing stacktraces.

Customer Impact

Customers would see exceptions with suspiciously long stacktraces:

aspnet/KestrelHttpServer#2745
aspnet/SignalR#2672

Regression?

No

Risk

Only the way we use ExceptionDispatchInfo inside pipe changes. No other logical changes.

[joshfree]

@muratg @halter73 please review this backport to /release/2.1

[joshfree]

Approved

[halter73]

I just realized this change creates an undesired behavioral change where if you complete a pipe with multiple exceptions, the last exception is now thrown from the other side instead of the first one.

[halter73]

I think we'll have to fix this in master too.

[pakrym]

I updated this PR to include behaviour fix from #31685

[karelz]

@pakrym @muratg what are the next steps here?

[pakrym]

This is ready to be merged. #31685 fixed tests failures we were seeing in master.

[pakrym]

This PR was updated with a regression fix. I'm going to remove NO MERGE label and merge the PR.

/cc @joshfree

[karelz]

@pakrym did you get shiproom approval? cc @danmosemsft

[pakrym]

I got it for 2.1.4 and then we discovered a regression and postponed merging.

[pakrym]

I re-added servicing considered label and would wait for re-approval.

[pakrym]

@dotnet-bot test Linux x64 Release Build please

[danmoseley]

OK re-added consider label. Please update template if necessary.

[jamshedd]

Approved for 2.1.5