[🚀 Feature]: Add --enable-chrome-logs flag to chromedriver startup in all bindings

[cgoldberg]

Description

related to #16117

In all bindings, when we start chromedriver, we should pass the --enable-chrome-logs argument. This allows chromedriver to inherit the i/o streams from the browser process. Without this, we have no way to suppress or redirect browser i/o streams, which results in unwanted logging going to the user's console.

JavaScript bindings already do this, but all other bindings do not.

Note: I am not sure if Edge supports this or a similar flag.

[selenium-ci]

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

Selenium Triage Team: remember to follow the Triage Guide

[cgoldberg]

#16202 implements this in Python.

[cgoldberg]

I am closing this for now. Adding this arg seems to break launching Chrome if you don't have i/o redirected. This needs further investigation.

[nvborisenko]

Safe in .NET since now we always redirect stdio.

[cgoldberg]

Safe in .NET since now we always redirect stdio.

Thanks, I think it probably works in Python also, but I want to test some more. I'll re-open this issue if things look OK.