Gitpod CLI: Improve Segment logging

[filiptronicek]

Description

Only enables Segment logging when logging verbose output. It means that Segment errors do not get outputted to standard error, because it is not critical to the CLI's functionality.

Summary generated by Copilot

🤖 Generated by Copilot at 91af8d6

Add custom logger for telemetry package and expose log level option to user. This improves the visibility and control of the telemetry output in the local-app component.

Related Issue(s)

Fixes EXP-912

How to test

Personally, I tested by changing the client configuration of Segment to some bogus address.

In the first command, the error is not shown. In the second one, we use verbose output and therefore it is.

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - ft-improvebff3ba7aca
• 🔗 URL - ft-improvebff3ba7aca.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - ft-improve-telemetry-logging-gha.20247
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[mustard-mh]

If I'm a user, I don't care any respond / process for metrics / telemetry / error report () even in verbose mode

Maybe add another level tracing ?

[filiptronicek]

@mustard-mh fair enough, it maybe should be a different level altogether. Looping in @csweichel, any advice for telemetry logs?

[geropl]

Tested and works, ✔️ to unblock.

I like @mustard-mh suggestion to push it down to trace, but silencing it entirely is also fine I think. Leaving it to @filiptronicek to force the discussion here, to move it to a follow-up PR. 🧘

[filiptronicek]

While we are in preview, I will leave segment errors in verbose output. It would be great to add another logging level, but that adds some complexity, both technical and user-facing (we have --verbose, how would you turn on tracing?).

I also fixed auto-updating by properly proxying the manifest file.