Feat/weighted rate limiting

[MaximeMRF]

🔗 Linked issue

#15

❓ Type of change

• [x ] ✨ New feature (a non-breaking change that adds functionality)

📚 Description

This PR introduces the ability to pass a custom amount to the increment, consume, and decrement methods of the Limiter.

I'm developing a security/WAF package for AdonisJS. This feature allows for a scoring-based system where different security threats (e.g., path traversal vs. simple 404) can carry different "weights" or penalties.

For the amount parameter, I have currently implemented a fail-safe approach: if a user provides a value <= 0, it defaults to 1.

• Should we keep this fail-safe (silent fallback to 1)?

• Or should we throw a Exception to alert the developer that they are passing invalid data?

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

I will update the doc if the PR is accepted, no worries

[thetutlage]

Looks good. Thanks 👍🏽

Also, automatically falling back to a default amount does make sense, instead of throwing an exception.

[thetutlage]

Please send a PR for the docs 🙏

[MaximeMRF]

thanks, I will do it