Add support for connecting to existing browser session via Google Chrome's remote debugging feature

[sbabcoc]

https://www.youtube.com/watch?v=4F-laDV9Pl8
This video shows how to use this feature locally, but it's apparently possible to construct a servlet to make this work on Grid sessions: https://stackoverflow.com/questions/48585187/chrome-remote-debugging-in-a-seleniumgrid

Other references: https://stackoverflow.com/questions/6827310/chrome-remote-debugging-doesnt-work-with-ip
https://developers.google.com/web/tools/chrome-devtools/remote-debugging

Potentially applicable to all drivers (not just Chrome): https://tarunlalwani.com/post/reusing-existing-browser-session-selenium/

Question: Once references to the driver object go out of scope, does the server get closed automatically, or would this leave a zombie behind? I probably need to determine how to close the driver without terminating the browser session (if this is possible).