Feat/rate limiting

[sarah-obasi-analytics]

closes #252

[vercel]

@sarah-obasi-analytics is attempting to deploy a commit to the Abdulazeem's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@sarah-obasi-analytics 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

[Abdulazeem-code]

fix backend build error

[Abdulazeem-code]

fix backend build error

[Abdulazeem-code]

Update branch fix backend build error

[sarah-obasi-analytics]

Update branch fix backend build error

on it

[sarah-obasi-analytics]

fix backend build error

fixed, kindly merge and sorry for the delay, will ill

[Abdulazeem-code]

Closing: Rate limiting (Issue #252) is already implemented on main — the limiter is configured (100 req/15 min per IP, Redis-backed) and applied globally via app.use(limiter) in server.js. Tests exist at tests/rate-limit.test.js. This PR's diff also contains destructive regressions (removing helmet, strict CORS, soft-delete filters, asyncHandler, webhookRoutes, etc.) that would break the production build. Thank you for the contribution — the feature was merged in an earlier iteration.