Add configurable request body size limits by route group

[Chucks1093]

Summary
Add configurable request body size limits by route group

Scope

• add route-group body size limit settings\n- fail fast with clear error response\n- document defaults and overrides

Acceptance Criteria

• scoped change is implemented with no unrelated file churn
• docs/tests are updated where applicable
• contributor can validate the outcome locally

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[kimanicode]

@kimanicode has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I’d like to work on this issue because it improves API robustness and prevents abuse by enforcing clear, configurable request size limits. I have experience working with backend middleware, request validation, and route-level configuration in Node-based servers. I’d focus on implementing per-route-group limits, failing fast with clear errors, and documenting defaults and overrides so the behavior is easy to understand and validate.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kimanicode to this issue.

[Gozirimdev]

@Gozirimdev has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Please can you assign this to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Gozirimdev to this issue.

[drips-wave]

Congratulations, @Gozirimdev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Gozirimdev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Gozirimdev as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The PR has been open for over 24 hours without maintainer objections and thoroughly addresses the issue by implementing route-group specific body size limits, adding configuration variables, updating error handling, and providing architectural documentation. The code changes follow the requirements perfectly.

😎 @Gozirimdev: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.