Feat: Add Deep Dependencies endpoint

[AritraDey-Dev]

Which problem is this PR solving?

• Fixes Create dummy /deep-dependencies endpoint #6606

Description of the changes

• Adds the missing backend endpoint to support the Deep Dependencies graph in the UI.

How was this change tested?

• Ran the server: go run ./cmd/jaeger
• Ran Jaeger UI: npm start
• Opened http://localhost:5173/deep-dependencies?service=test and confirmed the graph renders.

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[Copilot]

Pull request overview

This PR adds backend support for the Deep Dependencies graph feature in the Jaeger UI by exposing a new HTTP endpoint that the frontend can consume.

• Adds /analytics/v1/dependencies endpoint that routes to the existing deepDependencies handler
• Applies proper middleware (OpenTelemetry route tagging and span naming) to the new endpoint
• Includes an integration test to verify the endpoint is accessible and returns the expected response structure

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
cmd/query/app/http_handler.go	Registers new /analytics/v1/dependencies route with proper middleware, reusing the existing deepDependencies handler
cmd/all-in-one/all_in_one_test.go	Adds integration test checkDeepDependencies to verify the new endpoint is accessible and returns valid JSON structure

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.