fix withdrawal queue and filtered responses

[Sadeequ]

I implemented a global exception filter for NestJS that catches all unhandled exceptions and returns a consistent JSON error envelope. The filter:

Uses @catch() without arguments to capture every exception type
Leverages HttpAdapterHost for compatibility with any HTTP adapter (Express/Fastify)
Returns a standardized error structure containing:
statusCode (HTTP status)
message (error description)
errorCode (custom code or status code as string)
timestamp (ISO 8601 format)
path (request URL)
requestId (unique identifier for correlation)
Extracts or generates a requestId from headers (x-request-id), request.id, or creates one
Logs errors with the requestId for traceability, including stack traces in development
Strips stack traces from production responses while logging them server-side
Is already registered globally in main.ts via app.useGlobalFilters()
The implementation meets all acceptance criteria: consistent error envelopes for 4xx/5xx responses, stripped stack traces in production with server-side logging, and requestId correlation. Note that the build currently shows pre-existing errors in other files unrelated to this change.

Related Issue:

CLOSES #478

CLOSES #479

[vercel]

@Sadeequ is attempting to deploy a commit to the vic's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

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