[BUG] Chromedriver breaks ftr test due to its latest version 112.0.1 no longer support node 14

[ananzh]

Describe the bug
See the following error when run functional test in remote env

yarn run v1.22.10
$ scripts/use_node scripts/osd bootstrap
 info [opensearch-dashboards] running yarn

$ scripts/use_node ./preinstall_check
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field "[email protected]" is incompatible with requested version "typescript@~4.5.2"
[3/5] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=16". Got "14.21.3"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
ERROR [bootstrap] failed:
ERROR Error: Command failed with exit code 1: /opt/hostedtoolcache/node/14.21.3/x64/lib/node_modules/yarn/bin/yarn.js install --non-interactive
          at makeError (/home/runner/work/OpenSearch-Dashboards/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:25045:11)
          at handlePromise (/home/runner/work/OpenSearch-Dashboards/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:23981:26)
          at processTicksAndRejections (internal/process/task_queues.js:95:5)
          at async installInDir (/home/runner/work/OpenSearch-Dashboards/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:23704:3)
          at async Project.installDependencies (/home/runner/work/OpenSearch-Dashboards/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:15168:5)
          at async Object.run (/home/runner/work/OpenSearch-Dashboards/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:9[18](https://github.com/ananzh/OpenSearch-Dashboards/actions/runs/4868740431/jobs/8682483768#step:12:19)8:11)
          at async runCommand (/home/runner/work/OpenSearch-Dashboards/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:56360:5)
          at async Object.run (/home/runner/work/OpenSearch-Dashboards/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:[27](https://github.com/ananzh/OpenSearch-Dashboards/actions/runs/4868740431/jobs/8682483768#step:12:28)8:3)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.

This is because chromedriver published 112.0.1 yesterday (https://www.npmjs.com/package/chromedriver?activeTab=versions) and it drops support on node 14 (giggio/node-chromedriver@2ea1845). The latest version we could use for now is 112.0.0.

Functional test sets up chromedriver using scripts/upgrade_chromedriver.js:

OpenSearch-Dashboards/.github/workflows/build_and_test_workflow.yml

Line 183 in ca0bb8f

run: node scripts/upgrade_chromedriver.js

In scripts/upgrade_chromedriver.js, we first check the installed Google Chrome version, extracts the major version

OpenSearch-Dashboards/scripts/upgrade_chromedriver.js

Line 71 in ca0bb8f

const majorVersion = versionCheckOutput?.match?.(/(?:^|\s)(9\d|\d{3})\./)?.[1];

Then we install or upgrade chromedriver based on that major version:

OpenSearch-Dashboards/scripts/upgrade_chromedriver.js

Line 77 in ca0bb8f

spawnSync(`yarn add --dev chromedriver@^${majorVersion}`, {

Here, the ^ symbol in the version string chromedriver@^${majorVersion} is what allows yarn to install the latest compatible version of chromedriver that matches the major version of Google Chrome. Since the installed Google Chrome major version is 112, it installs the latest compatible chromedriver version that starts with 112, which happened to be 112.0.1 at the time.

To Reproduce
Submit a commit and see functional test result in Actions.

Expected behavior
Since we will bump node to 18 in next release, we could add a tmp fix to hard code chromedriver to 112.0.0. Then revert it after node bumped to 18.