chore: merge master into develop

* fix: work with extremely large partial results

* fix tests

* try again

* chore(ci): update selenium-webdriver to latest

* fix tests

* udpate webdriverjs

The webdriverio CI job was failing with the error message:

    session not created: This version of ChromeDriver only supports Chrome version 109
    Current browser version is 111.0.5563.64 with binary path /usr/bin/google-chrome

Despite the job running the following steps:

    - browser-tools/install-chrome
    - browser-tools/install-chromedriver
    - run: npm run coverage --prefix=packages/webdriverio

And browser-tools/install-chromedriver automatically installing the
right version of chromedriver based on the previously installed chrome
version.[1]

This was because browser-tools/install-chromedriver installed the
chromedriver under /usr/local/bin/chromedriver while
packages/webdriverio/src/test.ts was using the chromedriver from the
chromedriver NPM package (which is currently set to ^109.0.0 in
package.json).

This commit changes the webdriverio test code to instead use the
system-wide installed chromedriver (that has been installed via
browser-tools/install-chromedriver) in a CI environment.

[1]: https://circleci.com/developer/orbs/orb/circleci/browser-tools#commands-install-chromedriver

…683)

The timeout was decreased in 6f5498e
to 20 seconds (apparently accidentally since that commit was classfied
as a refactor ... and it also didn't update the --help text accordingly).

This commit changes it back to 90 seconds to match the --help text.

* refactor(webdriverjs): make code more DRY

* refactor: make tests respect CHROMEDRIVER_PATH

* chore(puppeteer): allow using v19

* use lateset chromedriver

* fix cache path for v19

* try again

* fix(ci): add puppeteer executable path

* remove config file

---------

Co-authored-by: Colin Rotherham <work@colinr.com>

Co-authored-by: michael-siek <michael-siek@users.noreply.github.com>