[Epic] Better support for spanlinks in the product (trace views)

[shivanshuraj1333]

In messaging systems there are cases when in batch read, the parent span id is not injected in the consumer spans, instead, spans are linked with consumer spans using span links.

Resources:

• determining-the-parent-span-from-a-context

• https://github.com/open-telemetry/semantic-conventions/blob/main/docs/messaging/messaging-spans.md#batch-receiving

(below resources for additional context)

• https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#span
• https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spancontext
• https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md
• https://opentelemetry.io/docs/specs/otel/overview/#tracing-signal

This can break the checks we have eg https://github.com/SigNoz/signoz-otel-collector/blob/a9b7c298e835bde41b4a447eeeaadc0449f4096d/cmd/signozschemamigrator/schema_migrator/traces_migrations.go#L363

Issues that we faced:

• [UI] Not all services are present on the services page #6747

Research:

• Understand when parent id is being injected in consumer spans (semantic conventions, and implementation of it), and when parent id is injected as span links in consumer spans

Some conversation here on slack thread:
https://signoz-team.slack.com/archives/C02B85R4R0A/p1735915865562669