Fix order and robustness of CTRL_*_EVENTs

[lhecker]

• This fixes a regression in 391abaf, which caused attached clients
  to receive CTRL_CLOSE_EVENTs, etc., in oldest-to-newest order,
  while historically the opposite is expected.
• It also changes the behavior of ProcessCtrlEvents to dispatch
  these events no matter whether a client is already dead.
  This restores the Windows XP to Windows 8.1 behavior.

Both of these fixes would address the issue on their own.

Closes #15373

Validation Steps Performed

• CloseTest from our repository shows newest-to-oldest order again.
• node gets killed when run under npm and closing the tab.

[DHowett]

admin merge - arm64 vcpkg issue, remediated in main