[dotnet] implement high level API for WebDriver BiDi Log Events

[titusfortner]

Status

• Note that this is based on #14052 and I have it set to merge into that branch to make it easier to see what is specific to the commits in this proposal (except ignore the Navigation code I need to update the other PR)
• All the status limitations in that PR apply to this PR
• I just realized I need to write tests for removing events

Description

• Implements ConsoleMessageHandler event (which allows adding and removing events)
• implements JavaScriptErrorHandler event (which allows adding and removing events)
• It uses the .NET convention of making the users start and stop the monitoring separate from adding and removing the handler (this still seems weird to me), so StartMonitoringLogEntries and StopMonitoringLogEntries
• I've set the classes and methods to show they are beta and shouldn't be relied on yet (as kind of a feature toggle so we don't have to have everything figured out before we do anything)

Motivation and Context

This is the first part of implementing #13992 in .NET

Feedback

• While this implementation works, I'm mostly interested in the user-facing API. Does the test code represent how we want users to work with BiDi going forward? (especially based on what was discussed at the last Dev Summit)
• @p0deje / @shs96c does this update to the Bazel file look right for having separate tests with BiDi enabled, or is it overkill? I also need to figure out how to tag specific tests to also have them run as part of dotnet_bidi_test_suite

[titusfortner]

I'm closing this PR because we are re-evaluating how we want the .NET API to look like. We're investigating moving away from Events as they do not work great with async pattern. It does not make sense to hold this PR open while waiting for that work.