events from private provider not getting fired if process starts after event collection starts

[Maoni0]

fixes #115420. please see description of the problem in that issue.

The key problem is that ETW doesn't guarantee the handle is initialized prior to running the callback. Trying to use the handle in the callback as an identifier doesn't work. Instead of the handle we can use the CONTEXT address which is already initialized at that time.

[Copilot]

Pull Request Overview

This PR fixes an issue where events from private ETW providers are not fired if a process starts after event collection begins. The fix changes how provider handles are compared in the ETW callback logic by comparing against the EtwProvider context directly rather than using RegistrationHandle.

Key changes:

• Updates provider handle comparison logic to use EtwProvider context instead of RegistrationHandle
• Adds missing stress trace handle declaration and usage
• Refactors if-else chain formatting for consistency

[Maoni0]

/ba-g dotnet/dnceng#6004