Add traceid to Apollo MCP Server logs for every transaction

[riginoommen]

Summary
Troubleshooting is slower because logs cannot be directly correlated with traces. We need each transaction log entry to include a trace identifier in the format traceid="xx" so engineers can immediately find the matching trace in Jaeger/Grafana.

Description
As an operator of the Support Case MCP Server, I need to see traceid="xx" in logs for every transaction, so I can trace each request end-to-end across MCP, Router, and downstream services without manual correlation steps.

Requirement
Every transaction/request log line must include:
traceid=""
This should be present for successful, failed, and timed-out transactions.

Why
Enables fast incident triage.
Removes guesswork when mapping logs to distributed traces.
Improves production support and root-cause analysis.
at present we have to search for transaction in the system manually

Acceptance Criteria
For each incoming transaction, logs include traceid="...".
traceid value matches the distributed trace shown in observability tools.
Present in all key lifecycle logs (initialize, call_tool, downstream GraphQL call outcomes, errors).
Verified in local and deployed environments with sample requests.