[WIP] Add vscode-tekton to the plugin registry

[ericwill]

WIP as the sidecar container has not been finished -- I am using my own quay repo for testing.

Closes eclipse-che/che#15752

Signed-off-by: Eric Williams ericwill@redhat.com

[ericwill]

Sidecar image work is ongoing here: che-dockerfiles/che-sidecar-tekton#2

[che-bot]

@ericwill Happy Path PR check [build 53] failed.

Re-trigger by [ci-test] or [ci-test-happy-path].

Link	URL
console	https://ci.centos.org/job/devtools-che-plugin-registry-pr-check-happy-path/53/console
artifacts	http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/53/

Depending on failure reason, the artifacts or deployment may not be present.

[che-bot]

@ericwill Happy Path PR check [build 54] failed.

Re-trigger by [ci-test] or [ci-test-happy-path].

Link	URL
console	https://ci.centos.org/job/devtools-che-plugin-registry-pr-check-happy-path/54/console
artifacts	http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/54/

Depending on failure reason, the artifacts or deployment may not be present.

[ericwill]

Testing on hosted Che I can see the plugin initialize, but it shows a message Please install the OpenShift Pipelines Operator.

[che-bot]

Happy path tests passed.

[sunix]

would it be possible to also include the tekton ext to the openshift plugin ? so if you install openshift 4.4, user would have Openshift pipeline and it would make sense to have it by default.

[gattytto]

would it be possible to also include the tekton ext to the openshift plugin ? so if you install openshift 4.4, user would have Openshift pipeline and it would make sense to have it by default.

yes you would need to add TKN binary to the openshift sidecar and maybe some more steps, I found this about TKN binary running pipeline in openshift 4.3 https://ibm-cloud-architecture.github.io/cloudpak-for-applications/liberty/liberty-deploy-tekton/

[ericwill]

Superceded by #503