feat: Update VS Code extension Camel K to v0.0.26

[apupier]

What does this PR do?

Upgrade to the newer version of VS Code Camel K 0.0.26. it provides kamel cli 1.5.0 by default.

Screenshot/screencast of this PR

What issues does this PR fix or reference?

https://issues.redhat.com/browse/CRW-2106

eclipse-che/che#20163

How to test this PR?

https://issues.redhat.com/browse/CRW-609?focusedCommentId=13990929&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13990929
https://developers.redhat.com/blog/2020/01/24/apache-camel-k-development-inside-eclipse-che-iteration-1

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
• 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.

Release Notes Text

Upgrade VS Code extension Camel K to v0.0.26

[apupier]

/retest

[apupier]

errors doesn't seem to be related to the PR (but I do not understand it very well):

==================== FINISH REPORT ========================
    JavaPlugin-------PASSED
    TypescriptPlugin-------FAILED
[ERROR] The plugin tests failed.
===========================================================
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2021-07-21T14:07:19Z"}
error: failed to execute wrapped command: exit status 1 
INFO[2021-07-21T14:07:29Z] Step plugins-test-pr-check-plugins-pr-check failed after 20m40s. 
INFO[2021-07-21T14:07:29Z] Running step plugins-test-pr-check-gather-aws-console. 
INFO[2021-07-21T14:07:49Z] Step plugins-test-pr-check-gather-aws-console succeeded after 20s. 
INFO[2021-07-21T14:07:49Z] Running step plugins-test-pr-check-gather-must-gather. 
INFO[2021-07-21T14:10:19Z] Step plugins-test-pr-check-gather-must-gather succeeded after 2m30s. 
INFO[2021-07-21T14:10:19Z] Running step plugins-test-pr-check-gather-extra. 
INFO[2021-07-21T14:12:39Z] Step plugins-test-pr-check-gather-extra succeeded after 2m20s. 
INFO[2021-07-21T14:12:39Z] Running step plugins-test-pr-check-gather-audit-logs. 
INFO[2021-07-21T14:13:09Z] Step plugins-test-pr-check-gather-audit-logs succeeded after 30s. 
INFO[2021-07-21T14:13:09Z] Running step plugins-test-pr-check-ipi-deprovision-deprovision. 
INFO[2021-07-21T14:19:00Z] Step plugins-test-pr-check-ipi-deprovision-deprovision succeeded after 5m50s. 
INFO[2021-07-21T14:19:00Z] Releasing leases for test plugins-test-pr-check 
INFO[2021-07-21T14:19:00Z] Ran for 1h22m49s                             
ERRO[2021-07-21T14:19:00Z] Some steps failed:                           
ERRO[2021-07-21T14:19:00Z] 
  * could not run steps: step plugins-test-pr-check failed: "plugins-test-pr-check" test steps failed: "plugins-test-pr-check" pod "plugins-test-pr-check-plugins-pr-check" failed: the pod ci-op-nwh5nbpg/plugins-test-pr-check-plugins-pr-check failed after 20m30s (failed containers: test): ContainerFailed one or more containers exited
Container test exited with code 1, reason Error
---
d]
[14:06:36] Read PostgreSQL logs...done [title changed]
[14:06:36] Read PostgreSQL logs...done [completed]
[14:06:36] Read Keycloak logs [started]
[14:06:36] Read Keycloak logs...done [title changed]
[14:06:36] Read Keycloak logs...done [completed]
[14:06:36] Read Plug-in Registry logs [started]
[14:06:36] Read Plug-in Registry logs...done [title changed]
[14:06:36] Read Plug-in Registry logs...done [completed]
[14:06:36] Read Devfile Registry logs [started]
[14:06:36] Read Devfile Registry logs...done [title changed]
[14:06:36] Read Devfile Registry logs...done [completed]
[14:06:36] Read Eclipse Che Dashboard logs [started]
[14:06:37] Read Eclipse Che Dashboard logs...done [title changed]
[14:06:37] Read Eclipse Che Dashboard logs...done [completed]
[14:06:37] Read namespace events [started]
[14:06:37] Read namespace events...done [title changed]
[14:06:37] Read namespace events...done [completed]
Command server:logs has completed successfully in 00:02.
The TypescriptPlugin pod exit code: + EXIT_CODE=1
[ERROR] The TypescriptPlugin plugin test failed.
pod "typescript-debug-plugins" deleted
Using https://che-eclipse-che.apps.ci-op-nwh5nbpg-b6833.origin-ci-int-aws.dev.rhcloud.com/api server API URL to log in
Successfully logged into https://che-eclipse-che.apps.ci-op-nwh5nbpg-b6833.origin-ci-int-aws.dev.rhcloud.com/api as user
Workspace ID: workspace62eegbougjac2pkz
Workspace workspace62eegbougjac2pkz successfully stopped.
Workspace with id 'workspace62eegbougjac2pkz' deleted.
==================== FINISH REPORT ========================
    JavaPlugin-------PASSED
    TypescriptPlugin-------FAILED
[ERROR] The plugin tests failed.
===========================================================
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2021-07-21T14:07:19Z"}
error: failed to execute wrapped command: exit status 1

[apupier]

based on history, it is always failing https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/pull-ci-eclipse-che-che-plugin-registry-main-v7-plugins-test-pr-check with a similar error

[openshift-ci]

@apupier: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Rerun command
ci/prow/v7-plugins-test-pr-check	b8213b0	link	/test v7-plugins-test-pr-check

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[svor]

@apupier openshift-ci errors are not related to your changes, we have an issue for that

[svor]

@apupier I see some errors related to Camlek extension but looks like it was started:

[apupier]

The completion is provided by the VS Code language Support for Apache Camel, not the VS Code tooling for Apache Camel K.
For scenarii to test:

• https://issues.redhat.com/browse/CRW-609?focusedCommentId=13990929&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13990929
• https://developers.redhat.com/blog/2020/01/24/apache-camel-k-development-inside-eclipse-che-iteration-1

We can see 2 error messages in output log:

• about mvn missing. This can be ignored. Mvn is not provided as vscode-java is nto working with vscode-camelk inside Che and so not provided. Mvn is required only when vscode-camelk is using features of vscode-java.
• about missing "Integration" resource type. This is because Che doesn't support to have a Camel K instance provided by default. Consequently, it is up to the user to configure a Camel K instance and configure the che workspace to connect to it.

We can see 2 messages as popup:

• kubectl version outdated. This is because the sidecar for kubernetes extension sidecar has not been updated for a while. Reported Upgrade minikube from 1.18.1 to 1.22.0 in VS Code kubernetes sidecar che#20173
• Activating xml extension failed. This is a bug for VS Code XML or Che. There is a real dependency on vscode-commons extension but there is a skipDependencies defined in registry. Upgrading to xml 0.17.0 should fix that as the dependency has been removed to vscode-commons but the vs code api required is wrongly mentioning 1.37.0 see [regression]Failed to run the "vscode-xml" plugin because of absence of the "redhat.vscode-commons" dependency che#20094

[svor]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: apupier, svor

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment