Allow visually debugging webdriver tests locally

[bduffany]

When running bazel tests with --config=webdriver-debug, tests will now spawn the GUI for chrome (instead of running in --headless mode), so you can see what the test is doing.

If the test fails, the browser window will stay open for 3s so you can see what state the app is in when the failure happened. This duration can be extended further so you can go in and check devtools etc., by setting --test_arg=-webdriver_end_of_test_delay=1h (this is super rudimentary for now; there is probably a better way to do this).

Also when running under this debug config, pass --verbose to chromedriver, so that if chrome crashes on startup, the root cause will be logged (by default, it logs a super opaque error just saying that chrome has crashed).

Tangentially related: this PR also updates the Go repo version for rules_webtesting to match the http_archive version in /WORKSPACE (the Go repo was behind the WORKSPACE repo due to bazelbuild/rules_webtesting#452)

rec-2023-02-02_14.12.35.mp4

---

Version bump: Patch

[maggie-lou]

Nice! I kept manually adding support for this while developing the webdriver tests - will be much nicer to have a config