[Automation] - Adjust cypress execution to generate html report on Jenkins

[izaac]

Summary

Fixes #
rancher/qa-tasks#1549

Occurred changes and/or fixed issues

Adding logic to generate HTML reports in the multi branch Jenkins pipelines

Technical notes summary

Basically the json that extended the current cypress config was replaced with our own Jenkins config.
The Jenkinsfile was updated for retrieving the report files from the CI node. The corral package was also updated in a separate PR for this purpose, and these PRs are mutually dependent.
The cypress-mochawesome-report lib is added as devDependency in package.json

Areas or cases that should be tested

GA CI
Jenkins CI

Areas which could experience regressions

Automation jobs

Related

rancherlabs/corral-packages#65

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[izaac]

@yonasberhe23 @rancher-max I moved the json configuration that supplemented the cypress.config.ts in the repo root to a dedicated cypress config. I've tested and it's working on branches other than master (release-2.7 ..). Although I had to make changes to make it work on the others, like the testDirs set.

This will need backports of cypress/support/e2e.ts, package.json and yarn.lock to include cypress-mochawesome-reporter as devDependencies. Which should be an innocuous change for dashboard.

[izaac]

Related PRs:
DevDependency 2.9: #12163
DevDependency 2.8: #12164
DevDependency 2.7: #12165

[izaac]

This depends on the corral-package PR in the description. I'm still working on getting that merged