Adapt Telemetry Plug-in API to a single-host mode

[azatsarynnyy]

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

What does this PR do?

1. Fixes /client-ip service URL for a single-host mode.
2. When sending the telemetry events about an editor usage, filters out the messages that come from the output channels, like hosted-instance-log. As such messages are recognized as vscode.TextDocumentChangeEvents.
   See the details in Logging to the console from a plug-in may cause the cyclic messaging che#18598

Screenshot/screencast of this PR

What issues does this PR fix or reference?

closes eclipse-che/che#18503
closes eclipse-che/che#18489

How to test this PR?

To test that the PR fixes eclipse-che/che#18503:

1. Deploy Che in single host mode
   chectl server:deploy --platform=minikube --installer=operator --che-operator-cr-patch-yaml=patch.yaml
   where patch.yaml content is

apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  name: eclipse-che
spec:
  server:
    serverExposureStrategy: 'single-host'
  k8s:
    singleHostExposureType: 'native'

2. Start a Workspace with the custom Che-Theia editor (with this patch included)

components:
- type: cheEditor
  reference: https://raw.githubusercontent.com/chepullreq4/pr-check-files/master/che-theia/pr-945/simple/che-theia-editor.yaml

3. Open Chrome/FireFox DevTools and make any edit in a file.

4. Make sure that there's a request to /client-ip service and it returns the data.
   

5. Make sure the correct telemetry events are sent to Che-Theia backend, e.g.:
   

To test that the PR fixes eclipse-che/che#18489:

1. Start a Workspace.
2. Make any edit in a file.
3. Make sure that there's only one request to /client-ip service.

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.

Happy Path Channel

HAPPY_PATH_CHANNEL=stable

[dmytro-ndp]

[crw-ci-test --rebuild]

[che-bot]

✅ E2E Happy path tests succeed 🎉

See Details

• Jenkins job console

• logs and configs

• Happy path tests DevFile

• images:

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

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

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[RomanNikitenko]

Tested using How to test section:
I see only one request to /client-ip service when a workspace is started

Telemetry events are sent to Che-Theia backend:

[azatsarynnyy]

@RomanNikitenko thank you for testing it! 👍