[WIP] Add Tracing Feature for Curve

[Ziy1-Tan]

What problem does this PR solve?

Hi! I want to try GSoC 2023, this's my rough idea and some tests.
Issue Number: #2229

Problem Summary:

Improve CurveBS observability by introducing Opentelemetry C++ SDK, Support features:

• Visualization: export popular Monitoring Platforms: e.g. Zipkin, Jaeger
• Configurable: enable tracing, export url, batch size, export interval...
• Performance: impact: <1%
• Good design: modular, can be applied to other modules
• ...

when AioRead is called, trace is as follows:

┌─────────────────────────────────────────────┐
│  Client Span                                │
│  total time: 500ms                          │
│  status: OK                                 │
│  ...                                        │
│  ├── Server Span      ├──  Callback Span    │
│  │   duration: 200ms  │   duration: 100ms   │
│  │   status: OK       │   status: OK        │
│  │   ...              │   ...               │
└─────────────────────────────────────────────┘

What is changed and how it works?

What's Changed:

• integrate SDK
  • introduce SDK
  • basic tests
• AioRead/Write
  • nebd part (AioRead done/ AioWrite (WIP) )
  • curve client part
  • chunkserver part
• performan test: using fio
• docs:
  • design docs
  • manual (part)
• Deploy: integrate Zipkin or Jaeger into curveadm deploy

How it Works:

Side effects(Breaking backward compatibility? Performance regression?):

Check List

• Relevant documentation/comments is changed or added
• I acknowledge that all my contributions will be made under the project's license

[caoxianfei1]

@wu-hanqing

[Ziy1-Tan]

I've been a little busy lately, anyone can take it.