Create v2 devfiles for Getting Started samples

[l0rd]

Is your enhancement related to a problem? Please describe.

One of the sub-epics of Run Che workspaces using the DevWorkspace operator is to switch our samples from a v1 to v2 based devfiles.

Describe the solution you'd like

• Add v2 devfiles in our samples git repositories
• Implement a new "project samples" registry, alternative to the devfile registry
• Add a installation parameter to switch between devfile and sample registry as the source of the getting started samples
• Adapt tests to use devfile v2 based Getting Started samples

Related to #18666

Further details

A simple devfile v2 is the one available here.
We should use schemaVersion: 2.1.0 rather than schemaVersion: 2.0.0 (che-server support for it)
and the full updated reference is here.

Subtasks

• Add v2.1 devfiles, .che/che-theia-plugins.yaml, .che/che-editor in our samples git repositories (Florent's note: I think we should use .vscode/extension.json for almost all devfiles)
  • done for one example there: https://github.com/che-samples/java-spring-petclinic/tree/devfilev2
• Create a sample registry (metadata) Add new link entries in devfile registry for devfile v2 #19906
  • devfile registry update to include this new service
  • dashboard update to support it
• If devworkspace is deployed, dashboard should use the sample registry Display devfile v2 getting started in dashboard if DevWorkspace is enabled #19923
• Adapt QE tests Migrate E2E devfile tests from v1 to v2  #20913

[l0rd]

Moving it out of scope of STEP 2 of the devworkspace work as we won't be able to create all the samples devfiles. That will be postponed to STEP 3 and we need to discuss if we need to update the devfile samples.

[svor]

@apupier @sideeffffect @filipkroupa @AndrienkoAleksandr we are creating devfiles v2 for getting started samples (more information you can find in the description).
It's already done for some samples, you can check the progress in the spreadsheet. So, I'd like to ask you to take care about the samples which you have contributed.

The procedure should be:

• Create a new branch in sample's repository (if you don't have permissions ask me)
• Add devfile.yaml version 2. Here you can find Devfile V2 API, also you can look at existing devfile v2 for quarkus sample
• Add the link to the branch with devfile v2 into meta.yaml in che-devfile-registry, for example take a look at quarkus meta.yaml

If you have any question, please ask me.

[sideeffffect]

@svor here are the PRs for Scala/Metals:

• Add devfile.yaml v2 che-samples/scala-sbt#1
• (feature) Scala: add link to v2 devfile che-devfile-registry#503

[max-cx]

Hi, a question to the assignee of this issue:

Will the outcome require any changes to the relevant content of the Installation Guide or Administration Guide or End-user Guide?

Yes/No?

[svor]

I'm going to close this issue. The following tasks were created:

• Migrate che4z devfile [devfile] Migrate che4z devfile to version 2  #20950
• Migrate E2E devfile tests from v1 to v2 Migrate E2E devfile tests from v1 to v2  #20913