refactor: migrate tracing core from boot-start to dubbo deployer

[conghuhu]

What is the purpose of the change

The previous Dubbo Tracing implementation overly relied on the spring boot starter. While providing users with better extensibility, Dubbo Tracing also loses its independence.

So I migrated tracing core from boot-start to dubbo deployer.

Child Task of #12448

Brief changelog

• Add dubbo-tracing module.
• Migrated OpenTelemetry tracer, Brave will migrate in the next PR.
• Transfer zipkin and otlp exporters in OpenTelemetry. Brave's zipkin will be migrated in the next PR.

Usage

Use SpringBoot Starter

        <dependency>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo-spring-boot-tracing-otel-zipkin-starter</artifactId>
        </dependency>

Use Dubbo directly

        <!-- dubbo tracing & tracing bridge & exporter -->
        <dependency>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo-tracing</artifactId>
            <version>${project.version}</version>
        </dependency>
        <dependency>
            <groupId>io.micrometer</groupId>
            <artifactId>micrometer-tracing-bridge-otel</artifactId>
        </dependency>
        <dependency>
            <groupId>io.opentelemetry</groupId>
            <artifactId>opentelemetry-exporter-zipkin</artifactId>
        </dependency>

Verifying this change

Local test result:

dubbo-samples：apache/dubbo-samples#854

TODO

• Add Non SpringBoot starter Sample in dubbo-samples.
• Migrate Brave.

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[conghuhu]

@songxiaosheng @AlbumenJ @chickenlj PTAL

[codecov-commenter]

Codecov Report

Merging #12453 (096b6fb) into 3.2 (5f39404) will increase coverage by 0.62%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##                3.2   #12453       +/-   ##
=============================================
+ Coverage     68.58%   69.21%    +0.62%     
+ Complexity      338        2      -336     
=============================================
  Files          3607     1637     -1970     
  Lines        168096    67526   -100570     
  Branches      27971     9907    -18064     
=============================================
- Hits         115295    46738    -68557     
+ Misses        42759    16266    -26493     
+ Partials      10042     4522     -5520     

see 2055 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[AlbumenJ]

Mode ObservationSenderFilter to dubbo-tracing

[conghuhu]

ObservationSenderFilter

I've finshed to move ObservationSenderFilter @AlbumenJ

[songxiaosheng]

LGTM

[chickenlj]

So only when all the above three conditions are matched will we initiate DubboObservationRegistry?

[conghuhu]

Yes, due to the Observation.class was proposed after version 1.10 of micrometer, when users use springroot2.x, it defaults to 1.9.x, which means Observation.class is missing. We have made the corresponding judgment and provided users with debug level log prompts.

As for Option, this is the switch that determines whether Dubbo itself has enabled the Tracing function

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
25 Code Smells

47.0% Coverage
2.2% Duplication

[AlbumenJ]

dubbo_provider_requests_total is missing after this PR merged. Revert in ea35f7ed5c1d6d2a6ede821f1481eb5088254d28