[Feature] Add execution tracing with performance for MQE engine and BanyanDB storage about skywalking HOT 5 CLOSED

As most queries are very fast, we are going to use ns(1e+9 of a second) as the time unit. Less than 1 ns could be ignored.

from skywalking.

For example, when we apply for MQE(service_percentile{p='50,75'} - avg(service_percentile{p='50,75'})), the execution tracing should look like

- MQE expression, service_percentile{p='50,75'} - avg(service_percentile{p='50,75'})
  - duration: 100 ns
  - queries
     - MQE syntax analysis
        - duration: 10ns
        - error:
     - readMetricsValues(service_percentile)
        - duration:
        - server-side traces....
     - /* Multiple metrics queries if needed. */
     - /* We need to consider to flag concurrency queries if MQE supported to run in that mode. */
     - In-memory calculation
        - error:
        - duration:

from skywalking.

Besides the server-side(OAP) response, UI should trace the query cost from browser perspective, which provide extra information whether the query is slow due to pending on network or HTTP server queue.

from skywalking.

BanyanDB server-side is related to #10561.

from skywalking.

BanyanDB server-side is related to #10561.

I have approved that. It should be easy enough to be integrated. The only thing is, @hanahmily we need the new client version to make the codes work.

from skywalking.