Add distributed-tracing correlation from HTTP requestId to Soroban txHash

[josephchimebuka]

Summary

Propagate requestId through services into Soroban logs/metrics and link txHash so a single client request can be traced across API → DB → chain → outbox.

Why this matters

Support and incident response currently require manual log grepping across disconnected identifiers.

Where to work

• requestId middleware
• src/services/soroban.service.ts
• src/services/bet-audit.service.ts
• outbox / winston logger fields

What to implement

1. Thread requestId via AsyncLocalStorage or explicit ctx.
2. Include requestId on Soroban log lines and audit events.
3. Index/searchable field linking requestId ↔ txHash.
4. Document how to trace a failed bet in ops docs.
5. Tests assert correlation fields present.

Acceptance criteria

• Bet/claim logs include requestId and txHash together.
• Outbox events carry correlation ids.
• Ops doc with example query.
• Tests verify fields.

Done when

One request can be traced from HTTP to chain settlement.

Metadata

Field	Value
Difficulty	advanced
Complexity	high
Good first contribution?	no

[Olumide-01]

@Olumide-01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I have reviewed this issue and i have relevant experience on it. Please assign to me. I look forward to delivering an excellent work.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Olumide-01 to this issue.

[Skype-F]

@Skype-F has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer I am a developer, Allow me to professionally implement this task with precision and accuracy.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Skype-F to this issue.