Add in verbose error message and telemetry for SetWindowsHookEx failure

[arjunbalgovind]

Summary of the Pull Request

What is this about?
In #5414 the exceptions that users reported was related to the SetWindowsHookEx API failing. As per the docs and after the reaching out to the respective team, the suggestion was to use the GetLastError API to get a more detailed error code/message. In this PR I have modified the Message box that we were earlier displaying to show the error code as well as the error message as well, rather than the generic "Cannot install keyboard listener". This will allow us to get more details when users post the issue, since we do not have enough information to figure out the reason right now. The PR also adds telemetry to log this exception for KBM, FZ and SG.

PR Checklist

• Applies to [PT Run] System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception at startup #5414
• CLA signed. If not, go over here and sign the CLA
• Tests passed

Info on Pull Request

What does this include?

• show_last_error_message in common.h was modified to allow a different message box title, with default set to the earlier value.
• In KBM, FZ, SG and interop, when the SetWindowsHookEx return value is NULL, GetLastError is called along with show_last_error_message.
• A telemetry event was added for KBM, FZ and SG, which logs the error code, error message and method name. This is called after show_last_error_message, with the method name as the parent function name followed by SetWindowsHookEx (for example for SG it is OverlayWindow.enable.SetWindowsHookEx).
• As per this comment Added telemetry to ImageResizer Shell Extension code (dev/imageResizer) #1272 (comment) we can't have a generic telemetry event across all modules

Validation Steps Performed

How does someone test & validate?

• Build and run PowerToys
• Modify one of the SetWindowsHookEx checks to check non-null and validate that the message box appears.

[enricogior]

LGTM. Nice work.