Fix debugger proxies

[martintmk]

Details on the issue fix or feature implementation

Follow-up of #1379

Confirm the following

• I started this PR by branching from the head of the default branch
• I have targeted the PR to merge into the default branch
• I have included unit tests for the issue/feature
• I have successfully run a local build

[codecov]

Codecov Report

Merging #1384 (7c38c76) into main (22df640) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1384      +/-   ##
==========================================
- Coverage   83.68%   83.65%   -0.04%     
==========================================
  Files         269      268       -1     
  Lines        6429     6417      -12     
  Branches     1004     1002       -2     
==========================================
- Hits         5380     5368      -12     
  Misses        840      840              
  Partials      209      209              

Flag	Coverage Δ
linux	83.65% <100.00%> (-0.04%)	⬇️
macos	83.65% <100.00%> (-0.04%)	⬇️
windows	83.65% <100.00%> (-0.04%)	⬇️

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

Impacted Files	Coverage Δ
src/Polly.Core/ResilienceStrategy.TResult.Async.cs	100.00% <ø> (ø)
src/Polly.Core/ResilienceStrategy.cs	100.00% <ø> (ø)
src/Polly.Core/Utils/ResilienceStrategyPipeline.cs	100.00% <ø> (ø)
.../Utils/ResilienceStrategyPipeline.DebuggerProxy.cs	100.00% <100.00%> (ø)

[martincostello]

Any screenshots of the new behaviour with and without it expanded you can share?

[martintmk]

Any screenshots of the new behaviour with and without it expanded you can share?

I cannot print-screen either because VS keeps hiding it :D

But now the proxy is only applied to ResilienceStrategyPipeline, the others use default behavior so that endless expansion thing is gone.