[release/9.0-staging] Fix recursion issue found in PROCCreateCrashDump

[github-actions]

Backport of #110379 to release/9.0-staging

/cc @steveisok @mikem8361

Customer Impact

• Customer reported
• Found internally

As reported in #118049, when running an application on Linux as PID=1 (the primary process), the process can hang when there's an unhandled exception with crash dumps enabled. The primary process ends up sending a different signal (SIGSEGV) during abort() where we fail to terminate the process and end up spinning indefinitely.

The fix is to break out of PROCCreateCrashDump if we detect the process re-enters the function.

This was originally fixed in #110379, but did not get backported to 9.

Regression

• Yes
• No

Testing

Manual - triggering an unhandled exception as the primary process.

Risk

Low

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.

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

[jeffschwMSFT]

lgtm. please get a code review. we will take for consideration in 9.0.x

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.