Sidecar filesystem/content reader will not work in front-end plugins

[tsmaeder]

Describe the bug

We have two classes in che-sidecar-content-reader.ts and che-sidecar-file-system.ts which read files form the sidecar container. They are implemented with the che plugin api. However, these two classes don't make sense when the che api is run as a front-end API.

We should decide whether running the che api as a front end plugin API makes sense at all. If we decide it does, we need to find a way to cleanly exclude the part of the API (in particular, when building the webpack version of the API).

[tsmaeder]

T.b.h, I think the setup of those services in the plugin host process should be separated from the setup of the API (they provide nothing into the che API namespace): the services should be hooked up to the rpc instance somewhere in the setup up of the remote plugins host processs.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.