Fix exception leaking from filter in nativeAOT

[janvorli]

There is a bug in handling exceptions that occur in exception filters in nativeAOT. If such exception is not handled in the filter, it needs to be swallowed and the filter should behave as if it returned false. Instead of that, the current behavior is that debug build of the runtime asserts and the release build fails fast without any message.

This change fixes it by catching the exception in the exception handling code. It was also necessary to modify the stack frame iterator to let it unwind past the filter funclet instead of failing fast.

Closedotnet/runtimelab#188

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

There is a bug in handling exceptions that occur in exception filters in nativeAOT. If such exception is not handled in the filter, it needs to be swallowed and the filter should behave as if it returned false. Instead of that, the current behavior is that debug build of the runtime asserts and the release build fails fast without any message.

This change fixes it by catching the exception in the exception handling code. It was also necessary to modify the stack frame iterator to let it unwind past the filter funclet instead of failing fast.

Author:	janvorli
Assignees:	janvorli
Labels:	area-NativeAOT-coreclr
Milestone:	8.0.0

[jkotas]

Thank you!

[janvorli]

Test failure is a known issue: #84821