VTUI: Visualization for distributed tracing.

[jiekun]

Is your feature request related to a problem? Please describe

VictoriaTraces now rely on external visualization solution, like Grafana and Jaeger UI. It's great to have our own UI to minimize the efforts of using it.

Describe the solution you'd like

We can create UI for VictoriaTraces based on Tempo's APIs. Comparing to Jaeger's APIs, tempo's one is more powerful and support more query arguments. However, it's not necessary to keep sync with Tempo, as VTUI doesn't need to have complex visualization features.

We can define the 1st edition of API base on Tempo APIs (use different endpoints, for easier maintaining). And implement both (APIs for VTUI, a.k.a native APIs, and APIs for Tempo). And in the future, we should maintain our native APIs and 1-2 popular external APIs.

The native APIs should include the ability to:

1. search trace by trace_id
2. search traces by various attributes (resource attributes, scope attributes, span attributes, event attributes and probably link attributes).
3. LogsQL to search for traces.

Describe alternatives you've considered

No response

Additional information

No response

[jiekun]

Let change this issue into the VMUI for VictoriaTraces, so no need to request for minor changes on the shared VMUI with vlogs.