Plugin host throws exception at startup

[tsmaeder]

Describe the bug

When I switch to the "next" version of che-theia in any workspace and enable a plugin like "typescript", for example, the output of the "extension host (xxxx) log" show and exception at startup:

ERROR:Error: Cannot find module '@eclipse-che/theia-plugin-ext/lib/plugin/node/che-api-node-provider.js'
Require stack:
- /remote-endpoint/node_modules/@theia/plugin-ext/lib/hosted/node/plugin-host-rpc.js
- /remote-endpoint/node_modules/@eclipse-che/theia-remote/lib/node/plugin-remote-init.js
- /remote-endpoint/node_modules/@eclipse-che/theia-remote/lib/node/plugin-remote.js

Che version

happens on che.openshift.io, and a local install of che with nightly on docker-desktop

Steps to reproduce

Switch to che-theia:next in any workspace and enable at least one che plugin.

Runtime

• docker-desktop + K8S (include output of docker version and kubectl version)
• other: che.openshift.io

[tolusha]

@tsmaeder
Is it just the error or plugins don't work either?

[ericwill]

A duplicate of #17601, perhaps?

[tsmaeder]

@ericwill no, and error with a reason and a stack trace would show up in the log even now.

[tsmaeder]

@tolusha I don't know, but if che-api-provider.js cannot be loaded, potentially all che-related API would not be available. So if someone writes a plugin that uses che API and does not run in the main theia process, that would likely not work.

[tsmaeder]

I suspect this is als what is causing #17609