[CI] setup Chrome and utilize binary path

[kavilla]

Description

Within the CI, the virtual runner that we are utilizing has Chrome
installed already. The version of Chrome is installed periodically.

The most recent version of Chrome requires updates to dependencies
that drop support for Node 14.

This downloads chrome in the CI and then checks the chromedriver
from the environment variable TEST_BROWSER_BINARY_PATH.

Issues Resolved

See failures here:
https://github.com/opensearch-project/OpenSearch-Dashboards/actions/runs/4896112900/jobs/8742518044

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
  • yarn test:ftr
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov-commenter]

Codecov Report

Merging #3997 (3f1de15) into main (6e352ff) will increase coverage by 0.00%.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main    #3997   +/-   ##
=======================================
  Coverage   66.43%   66.44%           
=======================================
  Files        3229     3229           
  Lines       62067    62067           
  Branches     9599     9599           
=======================================
+ Hits        41236    41238    +2     
+ Misses      18527    18526    -1     
+ Partials     2304     2303    -1     

Flag	Coverage Δ
Linux	66.38% <ø> (ø)
Windows	66.38% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 3 files with indirect coverage changes

[joshuarrrr]

can we add a link or add commentary on why this version is what we need?

[joshuarrrr]

I'd like to propose merging this PR as-is to unblock other pending PR automation. And then we can follow-up with a more permanent fix, without blocking all other merges in the meantime.

[opensearch-trigger-bot]

The backport to 1.3 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-1.3 1.3
# Navigate to the new working tree
pushd ../.worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-3997-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0188d05234f3fc510202b27ae1a122a1d1606686
# Push it to GitHub
git push --set-upstream origin backport/backport-3997-to-1.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-3997-to-1.3.

[opensearch-trigger-bot]

The backport to 1.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-1.x 1.x
# Navigate to the new working tree
pushd ../.worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-3997-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0188d05234f3fc510202b27ae1a122a1d1606686
# Push it to GitHub
git push --set-upstream origin backport/backport-3997-to-1.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-3997-to-1.x.

[joshuarrrr]

@kavilla Should this be backported to 1.x/1.3? If so, we'll need to do so manually.