[Cypress] Investigate CI ::set-output annotations removal for rancher tests and build latest-std-ui

[mmartin24]

Task

This work cleaned up the ::set-output annotations for STD-UI tests #244
We should try the same for Rancher-UI tests and Build Latest-STD-UI image creation

[mmartin24]

Build Latest-STD-UI fixed here: #264

[mmartin24]

Updated in scenario_1_chrome_rancher_ui.yml/scenario_2_frefox_rancher_ui.yml cypress_image: cypress/browsers:node16.14.2-slim-chrome100-ff99-edge. This did not seem to fix the issue, but worked with Rancher-UI-2-Firefox #340. We may want to keep this image but needs more testing.

Later I updated in step Cypress run action cypress-io/github-action@v3 to cypress-io/github-action@v4. That did not solve it either. In fact, it brought a new table in the ci and another annotation warning:

Rancher-UI-2-Firefox #342

[rancher-firefox / cypress-epinio-installation](https://github.com/epinio/epinio-end-to-end-tests/actions/runs/3344411260/jobs/5538780408#step:3:1)
Unexpected input(s) 'headless', valid inputs are ['record', 'config', 'config-file', 'env', 'browser', 'command', 'start', 'start-windows', 'build', 'install', 'install-command', 'runTests', 'wait-on', 'wait-on-timeout', 'parallel', 'group', 'tag', 'working-directory', 'headed', 'spec', 'project', 'command-prefix', 'ci-build-id', 'cache-key', 'quiet', 'component']

[mmartin24]

Ok, after this initial work already done:

• Upgraded all flags with ::set-output name= to the new standard >> $GITHUB_OUTPUT Replace ::set-output by GITHUB_OUTPUT #250

we did these others to attempt remove the flags on Epinio Rancher tests:

• Bumped all Github actions to latest version to date: Cypress/bump actions node16 #243
• Updated qa image: Updating actions for qa image #264
• Bumped Cypress to version 10 and Browser versions: [Cypress] Bump Cypress to v10 #265
  • Bumped cypress-io/github-action@v4: Cypress/bump to ghactionv4 #268

I revised the code on our entire e2e and the flag still appears for Epinio Rancher tests. Either it is something hidden on Gtithub Actions or something inherited from Rancher Dashboard. Anyhow, I cannot keep investing time in further debug here. We will wait to see if the warnings disappear with future action upgrades or in case it is inherited from somewhere from UI, if it is spotted there.