Print verbose exception message for OutOfMemoryException if possible

[jkotas]

The process can often have enough memory to print verbose exception message when OutOfMemoryException is thrown. Try to print the verbose exception message for OutOfMemoryException first, and fallback to short message without any details only if that fails.

[Copilot]

Pull Request Overview

This PR modifies the exception handling logic in the CoreCLR to improve OutOfMemoryException reporting. The change removes the special case handling that prevented verbose exception messages for OutOfMemoryException and instead attempts to print detailed exception information first, falling back to a short message only if printing the verbose message fails.

Key changes:

• Removed early detection and special handling of OutOfMemoryException
• Simplified the stack overflow check logic
• Added exception handling to catch failures when printing verbose messages and provide a fallback for OutOfMemoryException

Comments suppressed due to low confidence (1)

src/coreclr/vm/excep.cpp:1

• The error handling logic is inconsistent. For OutOfMemoryException, only a message is printed, but for other exceptions, additional logging and event log operations are performed. This creates different error reporting behaviors that could make debugging more difficult. Consider providing consistent error handling for all exception types in the catch block.

// Licensed to the .NET Foundation under one or more agreements.

[jkotas]

Example:

GC.KeepAlive(new int[Int32.MaxValue]);

Before this change

Out of memory.

After this change:

Unhandled exception. System.OutOfMemoryException: Array dimensions exceeded supported range.
   at Program.<Main>$(String[] args)

[janvorli]

LGTM, thank you!