Uniform error handling & reporting

[yuyoyuppe]

Summary of the new feature/enhancement

Currently there's no established flow for reporting errors to the user, e.g. when some of the saved settings are missing/malformed or some system API call failed.
Also there're multiple places in the code where all exceptions are silently swallowed.

I suggest establishing error handling practice and reporting via e.g. floating tray notifications or logging, depending if whether an error is recoverable or not.

To sum up:

• handle exceptions/error codes instead of silently ignoring/crashing with them
• introduce some uniform mechanism for reporting recoverable errors to user

Sub task: log is saved to AppData\Local\Microsoft\PowerToys\

• Color Picker
• FancyZones
• File Explorer add-ons
• Image Resizer
• Keyboard Manager
• PowerRename
• PowerToys Run
• Shortcut Guide
• Settings
• Runner

Sub task: log is included in the Bug Report

• Color Picker
• FancyZones
• File Explorer add-ons
• Image Resizer
• Keyboard Manager
• PowerRename
• PowerToys Run
• Shortcut Guide
• Settings
• Runner

Sub task: all catch exceptions are properly handled or logged

• Color Picker
• FancyZones
• File Explorer add-ons
• Image Resizer
• Keyboard Manager
• PowerRename
• PowerToys Run
• Shortcut Guide
• Settings
• Runner

While investigating this, also update #8419

[enricogior]

We may consider to move this to milestone 0.15.

[enricogior]

Given the modules will become stand alone application, this work can wait until we are at that point.
Moving to 0.19 but more likely it will be done for 0.20 or 0.21