DebugSettings.LayoutCycleTracingLevel doesn't work as docs claim

[stevenbrix]

Describe the bug

The docs for DebugSettings.LayoutCycleTracingLevel imply that the information will be added to Stowed Exceptions, but this doesn't seem to be the case

Steps to reproduce the bug

1. create a blank app with a button which will induce a layout cycle crash:

    class WinUILayoutCycleButton: Button {
         override func onPointerPressed(_: PointerRoutedEventArgs!) throws {
            layoutUpdated.addHandler { [weak self] _, _ in
                try? self?.invalidateMeasure()
            }
            width = width - 1
        }
    }

2. click the button to induce a layout cycle crash
3. look at the dmp file, there isn't more stowed exception information

Expected behavior

I would expect the stowed exception information to be included in the dump.

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.5.6: 1.5.240802000

Windows version

No response

Additional context

I've seen the tracing output, but in order to get that you need a debugger attached, or do something like detour OutputDebugString to collect the logs (assuming that's the API being used, I don't think this code is open source).

It would be nice to have a logging API, somewhat similar to DebugSettings.BindingFailed or DebugSettings.XamlResourceReferenceFailed