Better abnormal exit condition support

[Geenz]

The viewer has a few different ways it can shut down:

• Normal shut down (user clicked "quit")
• Shutdown freezes (user clicked "quit" but we froze somewhere along the way)
• User forced to quit (macOS: force quit, Windows "End Task" in task manager)
• OS decided to terminate the app (can happen under any number of circumstances, for example, a graphics driver reset)
• Crashes (something went wrong in the viewer, and an exception was raised)

It would be great to detect the more abnormal shutdown cases. I suspect that the OS terminating the app outside of a crash isn't likely to look any different from a user forcing the viewer to quit, but it's something we should track anyways.

Test Plan

TBD

---

This repo is using Opire - what does it mean? 👇

💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #4651 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Geenz (replace 20 with the amount, and @Geenz with the user to tip).

📖 If you want to learn more, check out our documentation.

[akleshchev]

User forced to quit (macOS: force quit, Windows "End Task" in task manager)

On windows this triggers 'handleCloseRequest'/WM_CLOSE and viewer does:
A. pops up an 'Are you sure you want to quit?' and dies immediately after. This is suposed to be registered as a freeze by our statistics, but looks like there is a bug somewhere in freeze/logout freeze detection that needs to be fixed.
B. fires off a disconect when user has 'don't ask again' set, in which case it will be recognizeed as a shutdown freeze

Trivia:
User issued shutdown is supposed to be WM_SYSCOMMAND with SC_CLOSE than WM_CLOSE, application should also be in focus, so we should be able to check for those events/state and be able to distinguish a 'kill' from normal 'close'.

What can be done:
We definetely should try to fire a disconnect. Potentially can leave an error marker.

System shutdown

For windows we are supposed to handle WM_QUERYENDSESSION and WM_ENDSESSION messages to start app shutdown, but we aren't doing that.

OS decided to terminate the app (can happen under any number of circumstances, for example, a graphics driver reset)

Updating driver causes a crash with callstack for me. Resetting windows driver via Win+Ctrl+Shift+B does not close or crash viewer.
Need ideas what else can be done.