Add junit report for interop

[musienko-maxim]

What does this PR do?

• Regarding interoperability testing-requirement the test results should be saved in the Junit format

Screenshot/screencast of this PR

<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Mocha Tests" time="54.075" tests="5" failures="1">
  <testsuite name="Root Suite" timestamp="2024-09-16T19:33:13" tests="0" time="0.000" failures="0">
  </testsuite>
  <testsuite name="Login to Openshift console and start WebTerminal " timestamp="2024-09-16T19:33:14" tests="5" file="/home/mmusiien/che-projects/che/tests/e2e/dist/specs/web-terminal/WebTerminalUnderAdmin.spec.js" time="54.025" failures="1">
    <testcase name="Login to Openshift console and start WebTerminal  Open Web Terminal after first installation" time="13.742" classname="Open Web Terminal after first installation">
    </testcase>
    <testcase name="Login to Openshift console and start WebTerminal  Verify first started WTO widget and disabled state Project field under admin user" time="1.876" classname="Verify first started WTO widget and disabled state Project field under admin user">
    </testcase>
    <testcase name="Login to Openshift console and start WebTerminal  Check starting Web Terminal under admin" time="14.757" classname="Check starting Web Terminal under admin">
    </testcase>
    <testcase name="Login to Openshift console and start WebTerminal  Verify help command under admin user" time="7.187" classname="Verify help command under admin user">
      <failure message="expected &apos;Installed tools:\nCommand    Version …&apos; to match /oc.*\d+\.\d+\.\d+.*OpenShift CLI\nkubectl.*\d+\.\d+\.\d+.*Kubernetes CLI\nkustomize.*\d+\.\d+\.\d+.*Kustomize CLI\nhelm.*\d+\.\d+\.\d+.*Helm CLI\nkn.*\d+\.\d+\.\d+.*KNative CLI\ntkn.*\d+\.\d+\.\d+.*Tekton CLI\nsubctl.*\d+\.\d+\.\d+.*Submariner CLI\nodo.*\d+\.\d+\.\d+.*Red Hat OpenShift Developer CLI\nvirtctl.*\d+\.\d+\.\d+.*KubeVirt CLI\nrhoas.*\d+\.\d+\.\d+.*Red Hat OpenShift Application Services CLI\njq.*\d+\.\d+.*jq/" type="AssertionError"><![CDATA[AssertionError: expected 'Installed tools:\nCommand    Version …' to match /oc.*\d+\.\d+\.\d+.*OpenShift CLI\nkubectl.*\d+\.\d+\.\d+.*Kubernetes CLI\nkustomize.*\d+\.\d+\.\d+.*Kustomize CLI\nhelm.*\d+\.\d+\.\d+.*Helm CLI\nkn.*\d+\.\d+\.\d+.*KNative CLI\ntkn.*\d+\.\d+\.\d+.*Tekton CLI\nsubctl.*\d+\.\d+\.\d+.*Submariner CLI\nodo.*\d+\.\d+\.\d+.*Red Hat OpenShift Developer CLI\nvirtctl.*\d+\.\d+\.\d+.*KubeVirt CLI\nrhoas.*\d+\.\d+\.\d+.*Red Hat OpenShift Application Services CLI\njq.*\d+\.\d+.*jq/
    at Context.<anonymous> (/home/mmusiien/che-projects/che/tests/e2e/specs/web-terminal/WebTerminalUnderAdmin.spec.ts:90:28)]]></failure>
    </testcase>
  </testsuite>
</testsuites>

What issues does this PR fix or reference?

https://issues.redhat.com/projects/WTO/issues/WTO-306

How to test this PR?

Set up Junit report with env. var: SAVE_JUNIT_DATA Run the test as usual and getting results in Junit format

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix or new feature
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[dmytro-ndp]

@musienko-maxim : I would make sure the changes doesn't break Dev Spaces testing pipelines before merging.

Also, it's important to address Empty workspace PR check failure: https://github.com/eclipse-che/che/actions/runs/10890977641/job/30220875771

Run cd tests/e2e
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm ERR! code EUSAGE
npm ERR!
npm ERR! npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm ERR!
npm ERR! Invalid: lock file's [email protected] does not satisfy chromedriver@125.0.3

[dmytro-ndp]

@musienko-maxim : EmptyWorkspace PR check is still failing, but because of different reason not related to this PR https://github.com/eclipse-che/che/actions/runs/10900556810/job/30248419583:

  1) Empty Workspace test 
       Wait workspace readiness:
     TimeoutError: Waiting for element to be located By(css selector, .monaco-workbench)
Wait timed out after 1058ms
      at /tmp/e2e/node_modules/selenium-webdriver/lib/webdriver.js:907:17
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

  2) "after each" hook: deleteWorkspaceOnFailedTest for "Wait workspace readiness":
     Error: Could not obtain _oauth_proxy cookie from chromedriver, browser session may have been killed. No stored token present!
      at CheMultiuserAuthorizationHeaderHandler.get (/tmp/e2e/utils/request-handlers/headers/CheMultiuserAuthorizationHeaderHandler.ts:41:11)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async CheApiRequestHandler.get (/tmp/e2e/utils/request-handlers/CheApiRequestHandler.ts:97:57)
      at async ApiUrlResolver.obtainUserNamespace (/tmp/e2e/utils/workspace/ApiUrlResolver.ts:41:46)
      at async ApiUrlResolver.getWorkspacesApiUrl (/tmp/e2e/utils/workspace/ApiUrlResolver.ts:33:29)
      at async ApiUrlResolver.getWorkspaceApiUrl (/tmp/e2e/utils/workspace/ApiUrlResolver.ts:29:13)
      at async TestWorkspaceUtil.stopWorkspaceByName (/tmp/e2e/utils/workspace/TestWorkspaceUtil.ts:71:39)
      at async TestWorkspaceUtil.stopAndDeleteWorkspaceByName (/tmp/e2e/utils/workspace/TestWorkspaceUtil.ts:139:3)
      at async Context.deleteWorkspaceOnFailedTest (/tmp/e2e/specs/MochaHooks.ts:124:6)

I am checking PR with Dev Spaces...

[dmytro-ndp]

Running 'Ansible' RecommendedExtensions test against Dev Spaces from the PR branch add-junit-report-for-interop didn't show regression.