Unable to query the expected remoteAddress in the Dubbo instrumentation for certain versions.

Describe the bug

In the Dubbo instrumentation, I identified a compatibility issue with context.getRemoteAddress() in Dubbo versions 3.0.x and 3.1.x. In these versions, context.getRemoteAddress() returns null, which prevents the correct value from being retrieved in other contexts. This is a bug in Dubbo; for more details, please refer to issue.

Steps to reproduce

In above versions of Dubbo, can't get expected remoteAddress by https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/7364927e510004356acd5d1f17c95daf17e16f89/instrumentation/apache-dubbo-2.7/library-autoconfigure/src/main/java/io/opentelemetry/instrumentation/apachedubbo/v2_7/DubboRequest.java#L36

Expected behavior

In above versions of Dubbo, return corrected remoteAddress by https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/7364927e510004356acd5d1f17c95daf17e16f89/instrumentation/apache-dubbo-2.7/library-autoconfigure/src/main/java/io/opentelemetry/instrumentation/apachedubbo/v2_7/DubboRequest.java#L36

Actual behavior

In above versions of Dubbo, return null by https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/7364927e510004356acd5d1f17c95daf17e16f89/instrumentation/apache-dubbo-2.7/library-autoconfigure/src/main/java/io/opentelemetry/instrumentation/apachedubbo/v2_7/DubboRequest.java#L36

Javaagent or library instrumentation version

2.15.0

Environment

No response

Additional context

No response