Chrome 111 is not compatible with default HTTP Client

# Chrome 111 is not compatible with default HTTP Client

If ChromeDriver fails to start after the Chrome 111 update, add --remote-allow-origins=* to your ChromeOptions as a workaround. The underlying issue (Selenium's Java HTTP client setting the Origin header) was fixed in Selenium 4.9.0, so upgrade past that and drop the workaround.

## Context from the issue
gh:SeleniumHQ/selenium#11750: Issue SeleniumHQ/selenium#11750 (closed, 60 comments): ### What happened?

After the Chrome 111 update, you can no longer kick off a chromedriver instance unless you add an additional chrome option:

"--remote-allow-origins=*"

I submitted a bug with Google and they responded, and indicated this has to do with Selenium setting the origin header:

https://bugs.chromium.org/p/chromium/issues/detail?id=1422444

### How can we reproduce the issue?

```shell
Just update to chrome 111, and try and run a UI selenium test.

I am using Java and Junit.  See the link to the Chrome ticket for more details on how I was personally starting the...