Problem

service.peer semconv selection still uses special-case logic in SemconvStability, and it is unclear whether Java should:

• add a dedicated declarative config shape for service.peer, or
• keep special-case logic separate from the newer per-domain semconv config model

Relevant context

• SemconvStability semconv config work: Align SemconvStability with newer declarative semconv config model #18907
• Implementation PR: Align SemconvStability with newer declarative config #18908
• Current code: instrumentation-api/src/main/java/io/opentelemetry/instrumentation/api/internal/SemconvStability.java

Question

Should service.peer be brought under the newer declarative semconv config model, or should it remain a special-case compatibility path?