Better handle event reset in LoggingService

[YuliiaKovalova]

Fixes #
https://dev.azure.com/devdiv/DevDiv/_workitems/edit/2320135/

Context

Reset() method invocation sometimes causes exception System.IO.IOException: 'The handle is invalid.'.
Very likely it happens on application shutdown.
The assumption is:

• ShutdownComponent starts and gets the _lockObject
• It cleans up/disposes the events
• Meanwhile our logging thread is trying to use those same events without checking _lockObject in context of StartLoggingEventProcessing()

Changes Made

use the same lock in StartLoggingEventProcessing() to protect a handle from invalid state.

Testing

n/a

[SimaTian]

Can you try benchmarking this and checking how this behaves on a multithreaded build please?
I've tried running this on OrchardCore with 10 processes and it failed to finish any of the runs I've tried - it runs much slower at a glance, and then finally it stalls indefinitely. I suspect a deadlock but I'm not deep enough in the code to know for sure.
Steps to reproduce:

• attempt to clean via artifacts\bin\bootstrap\core\dotnet.exe build OrchardCore.sln -maxcpucount:10 -tl:true -t:Clean
• It normally finishes within ~7 seconds
• however it's locked for more than half of a minute or so.

had to kill dotnet externally to unlock, not responding even to Ctrl + C