Upgrade to cypress 12 (into feature/cypress12)

[cwperks]

Description

Creating Draft PR to understand what is required to migrate to Cypress 12 from Cypress 9.

• Cypress 10 release blog: https://www.cypress.io/blog/2022/06/01/cypress-10-release/
• Cypress 11 release blog: https://www.cypress.io/blog/2022/11/08/announcing-cypress-11/
• Cypress 12 CHANGELOG: https://docs.cypress.io/guides/references/changelog#12-0-0

For this PR to get the specs working I had to:

• Rename cypress/support/index.js -> cypress/support/e2e.js
• Turn off rule "cypress/unsafe-to-chain-command": "off" as there were 290 violations - I will file a follow-up issue to resolve the violations and re-enable the rule.
• Added specPattern to the e2e section of the cypress config
• The e2e section of the cypress config was added by another user with a similar PR, I copied that into here and the only modification I made was adding the specPattern into that section.

Cypress Migration Guide: https://docs.cypress.io/guides/references/migration-guide

Issues Resolved

#408

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[peterzhuamazon]

Possible replacement of this one PR:

• Cypress - version update from 9.5.4 to 12.8.1 #598

[peterzhuamazon]

Waiting:

• [NodeJS Upgrade] Add [email protected] for build and [email protected] / [email protected] for OSD integTest opensearch-build#3552
• [NodeJS Upgrade] Make [email protected] install from pre-compiled archive  opensearch-build#3558
• Update vanilla snapshot test to match with package.json and replace deprecated set-output #676
• [NodeJS Upgrade] Windows AMI add node16/18 and cypress opensearch-ci#291
• [NodeJS Upgrade] Add chromium installation to the windows ami opensearch-ci#293
• Update table vis test in dashboard_filtering_spec.js #682

[peterzhuamazon]

Hi,

The snapshot workflow has 1 error on cypress9 but 12 errors on cypress12, awaiting

• Update vanilla snapshot test to match with package.json and replace deprecated set-output #676

on cypress9: https://github.com/opensearch-project/opensearch-dashboards-functional-test/actions/runs/5075827470/jobs/9117419180?pr=676

on cypress12: https://github.com/opensearch-project/opensearch-dashboards-functional-test/actions/runs/5075709332/jobs/9117195732?pr=668

cc: @ananzh

PS: added @RyanL1997 to take a look together.

Thanks.

[ananzh]

Cypress functional test fixed PR: #682

[kavilla]

Is this still slated for 2.8?

[peterzhuamazon]

There are a lot more tests so we will postpone this.

[cwperks]

Rebasing to feature/cypress12. This will be worked on in a feature branch to determine all tests that need to be updated to upgrade cypress from v9 to v12.

[cwperks]

Could a maintainer of this repo please review this / merge this into the feature (feature/cypress12) branch?

I plan to open up issues in all of the dashboards plugin repos to ensure their tests run with Cypress12 and request that any dashboards plugin that needs to update tests make a PR against the feature/cypress12 branch to show the tests working.

Once all dashboards plugins have verified their tests run with Cypress12 we can proceed to merging the feature branch into main.

The migration guide for cypress can be found here: https://docs.cypress.io/guides/references/migration-guide

[peterzhuamazon]

This will need more changes from individual plugin repos.
And @cwperks @RyanL1997 will help with that meta issue.

Thanks

[opensearch-trigger-bot]

The backport to 2.x failed:

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

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-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-668-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 63aeb324b5378984cce6d7846d6c719d6c81428f
# Push it to GitHub
git push --set-upstream origin backport/backport-668-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

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