Add the debuggerAddress option to chromium.js

[bwalderman]

Description

Adding a setter for Chromium's debuggerAddress capability. This is available in other language bindings but was missing from the JS bindings.

Motivation and Context

Chromium-based drivers provide the debuggerAddress option to let the user attach to an already-running browser instance at the specified address instead of launching a new one. One example where this is useful is certain WebView2 (WV2) scenarios. Users may want to test the web portion of an app that embeds WV2, but need to launch the app outside WebDriver first and drill through some native UI in order to activate the WV2 they are trying to test.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• [ X] I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[AutomatedTester]

Thanks for the PR. Could you give a bit more context about why this is needed? Currently, we get the debugger address from the capabilities returned and allow the driver to figure out where to put it.

[bwalderman]

Thanks, I've updated the motivation in the PR description.