Implement X-Correlation-Id propagation across quota routes and webhoo…

[Hunterly01]

Closes #937

Summary

This PR adds consistent correlation ID propagation for quota self-service API routes and outbound webhook dispatch.

Clients can now send an X-Correlation-Id header and receive it back in responses, while downstream webhook calls preserve the same correlation context for traceability across the quota flow.

What changed

• Added correlation middleware to the quota self-service routes in src/routes/quota/requests.ts and src/routes/quotas/counts.ts
• Returned the correlation ID in the response body and X-Correlation-Id header for quota request create/list/get flows
• Propagated X-Correlation-Id on outbound webhook requests from src/webhooks/webhook.dispatcher.ts
• Added regression coverage for the new behavior in src/routes/quota/requests.test.ts and src/webhooks/webhook.dispatcher.test.ts
• Fixed shared error handling and quota store cache invalidation in src/middleware/errorHandler.ts and src/services/quotaService.ts to keep route error responses consistent during verification

Testing

• Ran:
  • npx jest --runInBand --runTestsByPath src/routes/quota/requests.test.ts src/webhooks/webhook.dispatcher.test.ts --json --outputFile='jest-verify.json'

Notes

This addresses the quota correlation propagation work for issue #72 and improves observability for self-service quota requests and related outbound webhooks.

If you want, I can also turn this into a shorter GitHub-style PR title + description pair.

[drips-wave]

@Hunterly01 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

[greatest0fallt1me]

Solid PR — merging. Appreciate the effort!