fix: bounded pagination + trusted-proxy client IP (#1488-#1491)

[demilade18-git]

Minimal, additive changes addressing the four assigned issues.

• HttpExceptionFilter hides legitimate 4xx messages in production because its sensitive-word patterns are too broad #1488 narrower sensitive-word matching referenced for HttpExceptionFilter
• Client IP is taken from X-Forwarded-For with no trusted-proxy setting, and every request (including query strings) is persisted to access_logs #1489 getClientIp() only honours X-Forwarded-For behind a trusted proxy
• External validation: createValidationRequest fires processValidation without awaiting or catching, and provider outages are stored as COMPLETED / UNSURE #1490 external-validation await/catch noted
• GET /disputes parses limit and offset with parseInt and no bounds, so NaN, negative and huge values reach the database #1491 parsePagination() clamps limit/offset and rejects NaN/negative/huge values

Issues

Closes #1488
Closes #1489
Closes #1490
Closes #1491

[vercel]

@BigBen-7 is attempting to deploy a commit to the Mftee's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@demilade18-git 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