Report unhandled async exceptions

[janvorli]

Async exceptions like the ThreadInterruptedException are explicitly prevented from logging unhandled exception details to console.

This change removes this special handling and lets them be reported as any other unhandled exception.

Close #107594

[Copilot]

Pull Request Overview

This PR modifies the CoreCLR runtime to report async thread exceptions (like ThreadInterruptedException) as unhandled exceptions, removing special handling that previously prevented these exceptions from being logged to console.

Key changes:

• Removes the IsAsyncThreadException function that identified async exceptions for special treatment
• Updates unhandled exception reporting logic to treat async exceptions like any other unhandled exception
• Adds comprehensive tests for ThreadInterruptedException handling on both main and secondary threads

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
src/coreclr/vm/excep.h	Removes declaration of IsAsyncThreadException function
src/coreclr/vm/excep.cpp	Removes IsAsyncThreadException implementation and its usage in exception handling logic
src/tests/baseservices/exceptions/unhandled/unhandled.cs	Adds test cases for ThreadInterruptedException on main and secondary threads
src/tests/baseservices/exceptions/unhandled/unhandledTester.cs	Adds test validation for ThreadInterruptedException unhandled exception output

Comments suppressed due to low confidence (1)

src/tests/baseservices/exceptions/unhandled/unhandled.cs:51

• The if-else chain should be consistently structured. The original if statement for "mainhardware" should be changed to else if to maintain proper control flow consistency with the rest of the conditional chain.

            else if (args[0] == "mainhardware")

[janvorli]

/ba-g the test failures are known - #117795