[release/6.0] Fix hang caused by calling Environment.FailFast on multiple threads

[github-actions]

Backport of #72566 to release/6.0

/cc @jkotas

Customer Impact

Crashing process hangs instead of exiting. It prevents crashing service to recover gracefully without unnecessary delay.

Testing

Targeted repro

Risk

IMPORTANT: If this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

[jeffschwMSFT]

Approved. We will take for consideration in 6.0.x.

cc @JulieLeeMSFT

[trylek]

LGTM

[carlossanlop]

@jkotas @trylek @mangod9 there is a CI leg that timed out and got cancelled. Looking at the title of this PR, do you think it is possible the failure is related?

Confirming this is the only thing left for me to merge this.

[jkotas]

there is a CI leg that timed out and got cancelled. Looking at the title of this PR, do you think it is possible the failure is related?

It is not related. It timed out during the build:

[ 93%] Linking CXX shared library libclrjit_win_x86_arm64.dylib
##[error]The operation was canceled

[carlossanlop]

Tactics approved.
Correct milestone applied.
CI failure is confirmed to be unrelated.
No OOB package authoring needed (native code).
Ready to merge.