Tracing ID is missing in the rpc call chain

[oewang]

Describe the bug
In the integration test of the dubbo framework, the request link from the client to the server is incomplete on zipkin

To Reproduce
Step 1, You need to locally download the ease-agent-test-demo project and install zipkin and zookeeper.
Step 2, Start the server and client of the dubbo3.x project, and start by adding easeagent as a java agent. The server is dubbo3.x-server, and the client is dubbo3.x-client project.
Step 3, Request the path: http://{your ip}:8081/dubbo/test/chain/{any characters} via http client or browser, and then check it on zipkin to reproduce the bug

Expected behavior
The dubbo request link from the client to the server is complete

Version
Easeagent 2.2.4

Configuration

• EaseAgent Configuration

# -------------------- dubbo ---------------------
## dubbo tracing
plugin.observability.dubbo.tracing.enabled=true
plugin.observability.dubbo.tracing.args.collect.enabled=true
plugin.observability.dubbo.tracing.result.collect.enabled=true
## tracing reporter config
reporter.tracing.sender.appendType=http
reporter.tracing.sender.enabled=true
reporter.tracing.sender.url=http://{your ip}:9411/api/v2/spans