[release/9.0-preview3] Revert #99140

[github-actions]

Backport of #100143 to release/9.0-preview3

/cc @lewing @EgorBo

Customer Impact

• Customer reported
• Found internally

[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]

Regression

• Yes
• No

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Testing

[How was the fix verified? How was the issue missed previously? What tests were added?]

Risk

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[jkotas]

Have we verified that this change is actually fixing the issue?

[lewing]

Have we verified that this change is actually fixing the issue?

Nope. we're waiting to hear from Rolf from main, I opened the backport just to make the potential need clear while they test.

[jkotas]

It is no longer crashing in the xamarin-macios codeflow PR: xamarin/xamarin-macios#20343 .

[EgorBo]

Filed a proper fix #100206, so I presume we should backport that one, although, this revert is also fine to merge since it fixes the problem too (validated)

[dkurepa]

looks like we want to close this PR?

[EgorBo]

looks like we want to close this PR?

Like I said - it's ok to merge this if the issue is blocking.
The PR exposed an existing bug so this revert brings back previous behavior, while we're working on a proper fix.