Feat/server request correlation propagation

[adefemiesther1-debug]

Closes #485
Overview
This PR introduces a distributed request correlation architecture across the server network ecosystem to eliminate visibility blind spots in our multi-service architecture. By creating a unified correlation ID layer at our ingress boundaries and setting up async context propagation, this change enables end-to-end request timeline visualizations, fast cross-service log filtering, and direct observability from a single entry point down through database operations and blockchain transactions.

Changes
Branch: Created and pushed feat/server-request-correlation-propagation.

Distributed Observability Architecture Components:

Ingress Correlation Middleware: Catches inbound API calls, parses existing tracing parameters, or stamps a unique, high-entropy correlation tracking ID onto the request lifecycle.

Async Context Tracker Mapping: Hooks the active tracking id directly into the server's native async task management execution context, resolving the need to pollute internal function parameters.

Structured Logger Integration: Updates the global log formatter to automatically map the tracing payload signature into standard output records.

Outbound Pipeline Injectors: Automatically decorates external API payloads, database SQL command profiles (via query comments), and blockchain transaction parameters with the target correlation string.

Architectural Properties & Safety Guards
Performance Overhead Minimalization: Async contextual mappings use low-allocation primitives to prevent memory or throughput latency penalties along high-frequency request routes.

Resilient Failback Execution: If context propagation is partially disrupted by missing headers or third-party node configurations, the system safely generates localized trace paths rather than panicking or rejecting the underlying user transaction.

Verification & Testing Checklist
[x] Local Schema Verification: Manually reviewed middleware pipeline processing layout and structure configuration parameters to guarantee trace formats resolve safely.

[x] Atomic Check-In Alignment: Grouped code layers cleanly under an explicit conventional commit pattern and upstreamed directly to origin.

[vercel]

@adefemiesther1-debug is attempting to deploy a commit to the paul joseph's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@adefemiesther1-debug Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[anonfedora]

You have conflicts