[🚀 Feature]: [dotnet] Avoid native C# events for logging purposes

[nvborisenko]

Description

Many years ago, when logging was not available for internal/external usage, we applied event based model to emit log messages.

For example:

selenium/dotnet/src/webdriver/DevTools/DevToolsSession.cs

Line 98 in 9b48eb1

public event EventHandler<DevToolsSessionLogMessageEventArgs>? LogMessage;

It means that selenium library always allocates new memory even when there are no active listeners. This allocation is unnecessary.

Have you considered any alternatives or workarounds?

Now we have internal mechanism for emitting log messages, users are able to react on them... globally... memory friendly... performant...

In this issue I propose to remove all "events" which were especially considered for logging purposes, and replace it with already available new logging mechanism.

[selenium-ci]

@nvborisenko, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[nvborisenko]

FYI @YevgeniyShunevych @RenderMichael as usual, your opinion is highly appreciated.

[YevgeniyShunevych]

I am against using classic .NET events in case of async functionality. But is it worse effort if DevTools (CDP) functionality is going to be deprecated and removed later, or it will not be so soon?