Prevent process crashes from unhandled exceptions in global keyboard hook callback

[Copilot]

Users reported frequent hard crashes that surfaced as an unhandled Win32 exception/JIT debug dialog while DesktopScroll was running. The failure mode is consistent with an exception escaping the low-level keyboard hook callback boundary.

• Root-cause containment

  • Wrapped GlobalKeyboardHookService.HookCallback(...) in a defensive try/catch so managed exceptions do not cross the Win32 hook boundary and terminate the process.

• Hook-chain safety

  • On callback failure, the handler now logs and still returns CallNextHookEx(...), preserving hook-chain behavior instead of crashing the app.

• Diagnostics quality

  • Updated error logging to capture the full exception payload (ex.ToString() via interpolation) for actionable postmortem detail.

private IntPtr HookCallback(int nCode, IntPtr wParam, IntPtr lParam)
{
    try
    {
        // existing key processing / handled path
    }
    catch (Exception ex)
    {
        RuntimeTrace.Write($"Global keyboard hook callback error: {ex}");
    }

    return CallNextHookEx(_hookHandle, nCode, wParam, lParam);
}

• Fixes Frequent app crashes #8

[0RuiAlvel0]

no changes made. I implemented the recommendation myself.