[Tests] Bumps chromedriver to v107

[tmarkley]

Description

• Aligns all versions of chromedriver
• Removes manual resolution of axios

Issues Resolved

N/A - follow-up from #1410 and related to #1298

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

[tmarkley]

Dependency tree for axios, this is how I addressed this manual resolution (after removing it and bootstrapping):

$ yarn why axios
yarn why v1.22.15
[1/4] Why do we have the module "axios"...?
[2/4] Initialising dependency graph...
warning Resolution field "typescript@4.0.2" is incompatible with requested version "typescript@~4.5.2"
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "axios@0.27.2"
info Has been hoisted to "axios"
info Reasons this module exists
   - "workspace-aggregator-59198173-6b89-4e89-98f7-bc432bb9c629" depends on it
   - Hoisted from "_project_#@osd#ui-shared-deps#axios"
   - Hoisted from "_project_#@osd#dev-utils#axios"
info Disk size without dependencies: "616KB"
info Disk size with unique dependencies: "728KB"
info Disk size with transitive dependencies: "1.09MB"
info Number of shared dependencies: 6
=> Found "chromedriver#axios@0.24.0"
info This module exists because "_project_#chromedriver" depends on it.
info Disk size without dependencies: "540KB"
info Disk size with unique dependencies: "588KB"
info Disk size with transitive dependencies: "588KB"
info Number of shared dependencies: 1
Done in 1.35s.

$ npm list axios
opensearch-dashboards@3.0.0 /workspaces/OpenSearch-Dashboards
├─┬ @osd/dev-utils@1.0.0 -> /workspaces/OpenSearch-Dashboards/packages/osd-dev-utils
│ └── axios@0.27.2 
├─┬ @osd/ui-shared-deps@1.0.0 -> /workspaces/OpenSearch-Dashboards/packages/osd-ui-shared-deps
│ └── axios@0.27.2  deduped
└─┬ chromedriver@100.0.0
  └── axios@0.24.0 

[tmarkley]

@kavilla how do we bump this version in the Docker image?

[AMoo-Miki]

@tmarkley I have #2990 to automate this at runtime.

[tmarkley]

@AMoo-Miki I just noticed that PR this morning, it's great! I've already updated this PR to remove these parts.

[AMoo-Miki]

We are still debating if we should employ the auto-installer or install a specific chrome version of our choosing during CI.

[codecov-commenter]

Codecov Report

Merging #3017 (56b6f49) into main (8732b1c) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3017   +/-   ##
=======================================
  Coverage   66.70%   66.71%           
=======================================
  Files        3219     3219           
  Lines       61477    61477           
  Branches     9418     9418           
=======================================
+ Hits        41008    41014    +6     
+ Misses      18229    18224    -5     
+ Partials     2240     2239    -1     

Flag	Coverage Δ
Linux	66.65% <ø> (+<0.01%)	⬆️
Windows	66.65% <ø> (ø)

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

Impacted Files	Coverage Δ
...ared/static/forms/hook_form_lib/hooks/use_field.ts	66.66% <0.00%> (+0.96%)	⬆️
packages/osd-optimizer/src/node/cache.ts	53.94% <0.00%> (+2.63%)	⬆️
...s/osd-optimizer/src/node/node_auto_tranpilation.ts	87.75% <0.00%> (+4.08%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[tmarkley]

I didn't event see Miki's PR #2990. I'll remove the changes to the workflow config.

[AMoo-Miki]

@peterzhuamazon will this change impact you adversely?

[peterzhuamazon]

@AMoo-Miki If they are not for 1.3.7 and 2.4.0, then no impact as far as I know.
Thanks.

[joshuarrrr]

It seems like we should have backported this to active branches - let me know if that's wrong.

[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-3017-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5da75c7cb01c35da40f36783e6ca0dd6dd4a6c54
# Push it to GitHub
git push --set-upstream origin backport/backport-3017-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-3017-to-1.x.

[tmarkley]

It seems like we should have backported this to active branches - let me know if that's wrong.

@joshuarrrr yeah I would've added those labels but I don't have permissions.