Add request correlation IDs and structured error metadata

[David-patrick-chuks]

Summary

Improve observability by attaching correlation-friendly metadata to requests and surfaced SDK errors.

Why this matters

When integrations fail in production, maintainers and adopters need enough context to trace what happened. Correlation IDs and richer error metadata improve supportability.

Scope

• Add correlation ID support at request level.
• Surface correlation metadata through error objects where available.
• Ensure the feature works with retries and hook-based instrumentation.
• Keep metadata exposure consistent and documented.

Acceptance Criteria

• Request correlation IDs can be configured or injected.
• Relevant error objects expose structured metadata.
• Tests cover metadata propagation behavior.
• Docs describe intended operational usage.

Dependencies

• Depends on Harden HTTP retry strategy with exponential backoff and jitter #5
• Depends on Add configurable request hooks for logging, metrics, and tracing #6