Fix BinderTracingTest

[mateoatr]

Takes the changes from #55225. This should fix #59531.

[ghost]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Takes the changes from #55225. This should fix #59531.

Author:	mateoatr
Assignees:	-
Labels:	area-AssemblyLoader-coreclr
Milestone:	-

[elinor-fung]

Takes the changes from #55225.

Minor clarification: I believe the key part is from 77da330 - which #55225 was on top of, so the full fix is here.

[jeffschwMSFT]

Approved. @Anipik this is a tell mode infra change (test). Can you merge once there is a good time?
@mateoatr is this change needed to unblock a failing CI?

[elinor-fung]

These tests are run on PR, so any PR after #59428 got merged - for example, #59476 and #59548 - will hit this (all CoreCLR runtime test legs fail).

[jeffschwMSFT]

@mateoatr can you take a look at the CI failures?

[agocke]

Failing CI was just network errors -- reran and everything's passed

[NikolaMilosavljevic]

These tests are run on PR, so any PR after #59428 got merged - for example, #59476 and #59548 - will hit this (all CoreCLR runtime test legs fail).

@elinor-fung how can I get my PR (#59548) to succeed - what would be the steps?

[elinor-fung]

@NikolaMilosavljevic I think closing and re-opening the PR should make it redo the merge against latest (that has this change) and test against that. Alternately, explicitly rebasing your branch to the latest release/5.0 and pushing it up would definitely do it.

[NikolaMilosavljevic]

@NikolaMilosavljevic I think closing and re-opening the PR should make it redo the merge against latest (that has this change) and test against that. Alternately, explicitly rebasing your branch to the latest release/5.0 and pushing it up would definitely do it.

Thanks!