`rpc.server.duration` metric description is incorrect

Describe the bug

The rpc.server.duration metric has a description that does not conform with the OpenTelemetry semantic convention. This creates an issue when used with OpenTelemetry instrumented services that emit the same metric from a different language SDK (ie: Go). The OpenTelemetry Collector's, Prometheus exporter will specifically drop a metric if received that has the same name but a different description from a metric previously received.

We have run into this issue on the OpenTelemetry Demo project, our workaround is to write a special transform rule to remove descriptions from offending metrics.

Steps to reproduce

Using the gRPC auto instrumentation library with metrics being exported.

Expected behavior

The description for the rpc.server.duration metric should be: Measures the duration of inbound RPC.

This is defined in the OpenTelemetry semantic convention for this metric.

Actual behavior

The description for the rpc.server.duration metric is: The duration of an inbound RPC invocation

Javaagent or library instrumentation version

1.30.0

Environment

No response

Additional context

https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation-api-semconv/src/main/java/io/opentelemetry/instrumentation/api/instrumenter/rpc/RpcServerMetrics.java#L42

Start at instrumentation-api-semconv/src/main/java/io/opentelemetry/instrumentation/api/instrumenter/rpc/RpcServerMetrics.java around line 42 and compare the rpc.server.duration description with the linked semantic convention. Done means the metric uses the specified description, with the relevant instrumentation behavior verified.