Adapt devfile v2 happy-path tests to verify editors and extensions functionalities

[l0rd]

Is your enhancement related to a problem? Please describe

This was initially part of this epic #18668

Now that the work to support theia running vs code extensions for workspaces started using devfile v2 has been completed, the happy path test should be updated if hasn't yet.

Describe the solution you'd like

The happy path test should use a factory link to a che-sample as https://github.com/che-samples/java-spring-petclinic/tree/devfilev2 (branch is devfilev2) ✔️
and verify that:

• the workspace is started successfully
• the Java LS works properly

Describe alternatives you've considered

No response

Additional context

No response

[benoitf]

some notes:

step1: replace gist with che-samples repository ✔️
step2: Add tests on language server (like it's done on devfile v1)

[dmytro-ndp]

Scope of E2E Happy path tests:

• Che Operator Happy Path tests: https://prow.ci.openshift.org/?repo=eclipse-che%2Fche-operator
• Che Theia Happy Path PR check: https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/Che/job/e2e/job/minikube/job/pr-check/job/che-theia-pr-check/
• Che Server PR Happy Path PR check: https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/Che/job/e2e/job/minikube/job/pr-check/job/che-server-pr-check/
  ....

Test scenarios:

• DevWorkspace Happy path test scenario with factory workflow: https://github.com/eclipse/che/blob/main/tests/e2e/tests/e2e_happy_path/DevWorkspaceHappyPath.spec.ts

• Happy path devfile v.1 test scenario with chectl workspace creation workflow: : https://github.com/eclipse/che/blob/main/tests/e2e/tests/e2e_happy_path/HappyPath.spec.ts

[sleshchenko]

After discussion with QE team.
Statements:

• We can't reuse devfile v1 happy path test scenario since it uses workspace created with chectl but not factory link;
• We can't reuse pieces from devfile v1 happy path test since QE has conversion that test scenario must be in one file;

The plan we agreed on:

• @musienko-maxim will copy-paste everything below https://github.com/eclipse/che/blob/main/tests/e2e/tests/e2e_happy_path/HappyPath.spec.ts#L90 into https://github.com/eclipse/che/blob/main/tests/e2e/tests/e2e_happy_path/DevWorkspaceHappyPath.spec.ts and check how it works.

Later possible action item for QE:

1. refactor tests to be able to use suites without copying-pasting;
2. or fully align Devfile v1 and Devfile v2 happy path tests to make them live in a single file;

Personally, I prefer the first a bit more since I assume at some stage we can have different features needed to be verified.

@dmytro-ndp please verify and let me now if inaccuracies present;

P.S. Also we identified the following issue that should be handled separately Centralize DevWorkspace Happy Path test #20421

[dmytro-ndp]

@sleshchenko: it looks accurate, thanks for summary!

[rhopp]

refactor tests to be able to use suites without copying-pasting;

As for this point - we already have something like this. It's being adapted by Devfile tests, but HappyPath test (devfile.v1) is not using this.
We have generalized (and parameterized) test steps for common workspace verification in folder testsLibrary. You can see how it's used for example here: https://github.com/eclipse/che/blob/main/tests/e2e/tests/devfiles/JavaMaven.spec.ts#L50-L60

[musienko-maxim]

The steps until Display source code changes in the running application and Validation of debug functionality were adapted. It was merged in PR: #20476
Currently we adpting: Display source code changes in the running application, Validation of debug functionality and

[sleshchenko]

Validation of debug functionality can't be added due #20536

it will be added into happy path test along with Display source code changes in the running application in the scope of #20537