Websocket migration

[a-arias]

Summary

We have some old Python test that used to test the WebSockets for the connection inside the pods shells, to be able to send commands like list directories, create folders and validate the results, this one is going to implement the same but for cypress current automation framework

Occurred changes and/or fixed issues

Technical notes summary

rancher/qa-tasks#1350 (comment)

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

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

[richard-cox]

@a-arias This is an interesting progression. Would you be able to provide some information on end goal?

[a-arias]

@a-arias This is an interesting progression. Would you be able to provide some information on end goal?

hi, we have some old python test that used to test the websockets for the connection inside the pods shells, to be able to send commands like list directories, create folders and validate the results, this one is going to implement the same but for cypress current automation framework.

[izaac]

@a-arias this is ready for review as per our two last sync ups correct?
@yonasberhe23 @IsaSih could you take a look at this too?

[izaac]

these are the original tests: https://github.com/rancher/rancher/blob/main/tests/validation/tests/v3_api/test_websocket.py

[izaac]

@a-arias I think the jenkins cypress.config has to be updated too for the Jenkins CI, https://github.com/rancher/dashboard/blob/master/cypress/jenkins/cypress.config.jenkins.ts

[izaac]

Paired reviewed offline. Troubleshooting this isn't working as expected when running on the same Rancher node as it's done in Actions. Tagging it for Jenkins.