Handle windows shutdown event

[sbomer]

By doing a clean EEShutdown, including calling ProcessExit handlers, as suggested by @stephentoub in #36089 (comment). This allows ProcessExit to respond to 'docker stop', which sends CTRL_SHUTDOWN_EVENT to windows containers. I'm doing the same for the logoff event.

Automated testing is challenging since I don't see a documented way to trigger these events (other than triggering a shutdown or running in a container). I tested this locally to confirm that it produces the desired behavior on 'docker stop', and will do more testing for the logoff and shutdown events outside of docker.

#36089 (comment) suggests removing removing if (dwCtrlType == CTRL_CLOSE_EVENT). This would cause ProcessExit to fire on an unhandled Ctrl+C (currently it does not on windows or unix), so I am making the more targeted change for 5.0.

Fixes #36089

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[sbomer]

Actually, this may require more thought for the logoff event. From https://docs.microsoft.com/en-us/windows/console/handlerroutine

When a console application is run as a service, it receives a modified default console control handler. This modified handler does not call ExitProcess when processing the CTRL_LOGOFF_EVENT and CTRL_SHUTDOWN_EVENT signals. This allows the service to continue running after the user logs off.

I assume that calling ProcessExit is ok for CTRL_SHUTDOWN_EVENT because the system will terminate the process shortly even if the handlers don't. But CTRL_LOGOFF_EVENT doesn't necessarily terminate the process, so maybe it would be better not to do an EEShutDown in this case, and instead provide a cancellable API for the logoff? @jkotas

[jkotas]

Sounds reasonable. We should make the fix as scoped as possible.

[jkotas]

Thanks!

[sbomer]

I confirmed that it also works as expected during windows shutdown for a service.

[vitek-karas]

Absolutely agree that for .NET 5 we should make this as small of a change as possible.
The logoff scenario is something we may want to look into for .NET 6 (can you please file an issue for it).

[sbomer]

/backport to release/5.0

[github-actions]

Started backporting to release/5.0: https://github.com/dotnet/runtime/actions/runs/218953220