[baseserver] Initialize tracer with server

[easyCZ]

Description

This change extends base-server to automatically initialize tracing as part of the server. It also adds a convenience method to retrieve the tracer with server.Tracer() rather than grabbing it from the global opentracing.GlobalTracer() namespace.

Related Issue(s)

Fixes #

How to test

• Existing tests for the lifecycle of baseserver cover the tracer being created, and closed
• Preview env

Release Notes

NONE

Documentation

Build Options:

• /werft with-github-actions
  Experimental feature to run the build with GitHub Actions (and not in Werft).
• leeway-no-cache
  leeway-target=components:all
• /werft no-test
  Run Leeway with --dont-test

Publish Options

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

Installer Options

• with-ee-license
• with-slow-database
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /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
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

/hold

[werft-gitpod-dev-com]

started the job as gitpod-build-mp-baseserver-tracer.1 because the annotations in the pull request description changed
(with .werft/ from main)

[easyCZ]

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-mp-baseserver-tracer.4
(with .werft/ from main)

[easyCZ]

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-mp-baseserver-tracer.5
(with .werft/ from main)

[geropl]

Code LGTM, deployment works and log look 👌 : ✔️

(although these big PRs that touch a gazillion .sum/.mod files scare me a bit 😬 )

[mads-hartmann]

LGTM. There are conflicts now - approving just so you don't have to chase down reviews after having resolved them

[mustard-mh]

/werft run

👍 started the job as gitpod-build-mp-baseserver-tracer.7
(with .werft/ from main)

[mustard-mh]

/werft run

👍 started the job as gitpod-build-mp-baseserver-tracer.8
(with .werft/ from main)

[mustard-mh]

/werft run recreate-vm

👍 started the job as gitpod-build-mp-baseserver-tracer.9
(with .werft/ from main)

[mustard-mh]

Workspace can be started in preview env

❓ But honeycomb shows nothing don't know how to verify it

gitpod /workspace/gitpod (mp/baseserver-tracer) $ kubectl get configmap otel-collector -n monitoring-satellite -o yaml | grep preview.name -C 3
    processors:
      attributes:
        actions:
          - key: 'preview.name'
            value: mp-baseserver-tracer
            action: insert
    exporters:

[easyCZ]

So this change only binds the Tracer. We don't use it in the public-api yet so we won't yet have traces showing up

[easyCZ]

/unhold