[🚀 Feature]: Any WebDriver may accept user-provided HttpMessageHandler

### Description

Explaining shortly: each webdriver creates own HttpMessageHandler (represents OS network connection). It's OK for local chromedriver which starts always on new port (different story). But it is not OK when I execute hundreds of tests (webdrivers) for remote service provider (grid, browserstack..)

Revisit how to manage lifecycle of HttpMessageHandler and how configure them to be potentially reused.

### Have you considered any alternatives or workarounds?

There is workaround, but it not so easy to use. Probably it is right "workaround", anyway, let explore how to improve.