Enable FailFastOnErrors property to better improve error diagnosis

[adrastogi]

Suggested new feature or improvement

Set the FailFastOnErrors property so that XAML errors will result in immediate crashes (thereby enabling easier diagnosis).

Scenario

This is feedback from the WinAppSDK folks who helped investigate some recent bugs, so filing this issue to help track it. The idea is to use the property documented below in Dev Home so that it is easier to find errors earlier and with more context, which is especially useful in cases where those errors might otherwise be ignored.

https://learn.microsoft.com/en-us/uwp/api/windows.ui.xaml.debugsettings.failfastonerrors?view=winrt-22621

Additional details

The documentation indicates that this can be set for apps in the Store as well. So we would likely want to do this in a progressive fashion (e.g., set this property, run through our test scenarios and see what crashes get surfaced, fix those, test again, etc.). Once we have a good baseline, we could consider enabling this globally in published versions of the application.

Tasks

Preview Give feedback

1. Fix FailFast crash on startup #3200
   +0
2. FailFastOnErrors causes crashes on startup and shutdown #3136
   Area-Core Issue-Bug Priority-2 Resolution-Fix-Available +4
3. Segment throws an error when FailFastOnErrors is true. CommunityToolkit/Windows#438
   +0
4. Leaving the main Windows Customization page causes a crash when FailFast is enabled #3300
   Area-Customization Issue-Bug Priority-2 +3

[krschau]

Besides the errors on startup and shutdown, I'm seeing one after clicking "set up local machine" in Machine configuration, although it doesn't bring down DH.