[🚀 Feature]: [dotnet] Consider separate `Selenium.WebDriver.DevTools` nuget package implementation

[nvborisenko]

Description

Currently:

• CDP is auto-generated and is a part of main Selenium.WebDriver package
• Internally Selenium.WebDriver relies on CDP implementation (magically in runtime, using the latest spec which is supposed to be compatible with last 5 versions)

Have you considered any alternatives or workarounds?

Ship CDP implementation as separate package:

• Selenium.WebDriver.DevTools v137.0.1.34
• Selenium.WebDriver.DevTools v137.0.2.83

The main Selenium.WebDriver package always rely on the latest released Selenium.WebDriver.DevTools package.
The main Selenium.WebDriver package always rely on the minimal required Selenium.WebDriver.DevTools package, which is stable v1.3.

[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

[RenderMichael]

We would need to move the JavascriptEngine and NetworkManager types into the Selenium.WebDriver.DevTools package as well, since they are implemented with CDP.

Moving the JavascriptEngine type should be no problem, but NetworkManager will be tricker. It is publicly exposed at driver.Manage().Network.

We already have an effort to restructure some driver namespacing on our plate for v5: #14065. We can wrap that in as part of this, exposing an extension method on IWebDriver to get or add the INetwork instance.

[nvborisenko]

No, .Manage().Network API still remains in main package.

[RenderMichael]

If .Manage().Network is part of the main package, then we can’t make this change until NetworkManageris rewritten in BiDi instead of CDP.

[nvborisenko]

No problems at all, just move generated types to another package.