Is your feature request related to a problem? Please describe.
Need to OTEL trace spans and generate Application Performance Monitoring (APM) service map relationships and metrics.

Describe the solution you'd like
The otel_apm_service_map processor analyzes OpenTelemetry trace spans to automatically generate Application Performance Management (APM) (aka Applicaiton Performance Monitoring) service map relationships and metrics. It creates structured events that can be visualized as service topology graphs, showing how services communicate with each other and their performance characteristics. As part of service map creation, the processor decorates client an server spans

Spans decoration for server span :

• aws.local.service
• aws.local.operation
• aws.span.kind
• aws.local.environment

Span decoration for client span :

• aws.local.service
• aws.local.operation
• aws.remote.service
• aws.remote.operation
• aws.remote.environment
• aws.span.kind

Topology extracts these informations. From Server span : It extracts ServiceName, Operation and Environment and make one document. It doesn’t need trace end to end view. For client span : It uses end to end trace view. client span topology picks local operation from parent server span, remote service and operation from child server span and service, kind and environment from itself.

What is APM ? - See https://en.wikipedia.org/wiki/Application_performance_management

Describe alternatives you've considered (Optional)
Alternately, the existing service_map processor could be modified to support this. But there are couple of ways (the way relationship are established at client and server side separately, and generation of RED metrics) this new processor is different and instead of changing the existing processor behavior, a new processor is developed. In future, it is possible to deprecate existing service_map processor but for now keeping separate would make it clean.

Customers requiring the more APM specific service map and associated metrics would have to choose the new service map processor, otherwise they can use the existing/old service map processor.

Additional context
Add any other context or screenshots about the feature request here.