Make it possible to build Che Theia based on upstream Theia commit

[azatsarynnyy]

Signed-off-by: Artem Zatsarynnyi azatsary@redhat.com

What does this PR do?

With the proposed changes it's possible to build Che Theia based on a particular commit of Theia.

By default, the build works without any changes - it takes the latest commit of Theia in master branch.
THEIA_COMMIT_SHA argument can be passed through the build.sh build-args.

Also, it's not needed anymore to set Theia version to THEIA_VERSION file before doing a release. It will be fetched from npmjs.org.

What issues does this PR fix or reference?

closes eclipse-che/che#16691
closes eclipse-che/che#16654

Release Notes

Docs PR

[che-bot]

✅ E2E Happy path tests succeed 🎉

See Details

• Jenkins job

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	docker.io/maxura/che-theia:737
che-theia-endpoint-runtime-binary	docker.io/maxura/che-theia-endpoint-runtime-binary:737

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

[benoitf]

tested with build.sh

👍

[benoitf]

I'm still wondering about THEIA_COMMIT_SHA, how does it change the yarn.lock dependencies of plug-ins, etc to use that version as well ? looks like it will still try to compile extensions/plugins with yarn.lock settings
it seems it's only managed by release script, not the build script

or should we have as well a parameter like --stick-to-yarn.lock in build.sh to use upstream theia referenced by the one inside the yarn.lock

[azatsarynnyy]

THEIA_COMMIT_SHA doesn't affect node build of the extensions/plugins.
It affects only upstream Theia build with our extensions/plugins included.