feat(kuma-cp): add tracing to KDS server

[michaelbeaumont]

Gives traces like the following:

Span #3
    Trace ID       : a8ec507e1548af1438b9f859da994763
    Parent ID      :
    ID             : b5183f331989f5a3
    Name           : kuma.mesh.v1alpha1.GlobalKDSService/StreamClusters
    Kind           : SPAN_KIND_SERVER
    Start time     : 2023-07-04 08:28:43.868995353 +0000 UTC
    End time       : 2023-07-04 08:42:12.451383472 +0000 UTC
    Status code    : STATUS_CODE_UNSET
    Status message :
Attributes:
     -> rpc.system: STRING(grpc)
     -> rpc.service: STRING(kuma.mesh.v1alpha1.GlobalKDSService)
     -> rpc.method: STRING(StreamClusters)
     -> net.sock.peer.addr: STRING(127.0.0.1)
     -> net.sock.peer.port: INT(48400)
     -> rpc.grpc.status_code: INT(1)

We'll probably have to experiment with these and see how useful they are and certainly add our own traces.

Checklist prior to review

• Link to relevant issue as well as docs and UI issues --
  propagate tracing information on api-server request/response #5696
  Document opentelemetry tracing in kuma-cp kuma-website#1397
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s) --
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? --
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?