If the signal occurs when heap being inconsistent we should not
use heap. We should call signal-safe functions only from signal handler.

fix https://github.com/dotnet/coreclr/issues/16338

This reverts commit fa6087f0c2856215e7141259b56e75b46746f74d.

If the signal occurs in not managed code we cannot use heap.
We should call signal-safe functions only from signal handler.

Create exception object on stack for checking source of signal.
If signal is from managed code we can use memory allocation to create
persistent exception on heap as copy of volatile exception on stack.

If signal from unmanaged code we do nothing and call base signal handler.

fix https://github.com/dotnet/coreclr/issues/16338

PAL_SEHException::EnsureExceptionRecordsOnHeap() moves exception record
to heap if needed.

fix https://github.com/dotnet/coreclr/issues/16338