test: remove redundant TestGetTraceWithRawTracesParameter

[aliyasirnac]

Which problem is this PR solving?

• Resolves a stale // TODO in http_handler_test.go. The test logic for the raw parameter was already implemented in TestGetTrace, making TestGetTraceWithRawTracesParameter redundant.

Description of the changes

• Removed TestGetTraceWithRawTracesParameter entirely.
• The raw query parameter behavior (asserting that raw=true yields 3 spans and raw=false yields 2 spans via deduplication) is already adequately covered by the existing TestGetTrace test earlier in the same file. Removing this function eliminates code duplication and reduces maintenance cost.

How was this change tested?

• Verified that make test and make lint still pass successfully without the redundant test.

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/main/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality (Not applicable, removed redundant test)
• I have run lint and test steps successfully: make lint test

AI Usage in this PR (choose one)

SeeAI Usage Policy.

• None: No AI tools were used in creating this PR
• Light: AI provided minor assistance (formatting, simple suggestions)
• Moderate: AI helped with code generation or debugging specific parts
• Heavy: AI generated most or all of the code changes

[Copilot]

Pull request overview

Extends Jaeger Query HTTP handler tests to validate the behavioral difference of fetching traces with and without the raw query parameter, specifically around span adjustment/deduplication.

Changes:

• Replaces the previous TODO-only TestGetTraceWithRawTracesParameter with an actual assertion using a trace containing a duplicate span.
• Converts the test to a table-driven form to validate both raw=true and raw=false cases via expected span counts.
• Validates the decoded JSON response contains the expected number of spans.

---

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