Rate Limiting docs is misleading for Websockets example

[zenstok]

I'm submitting a...

• Regression
• Bug report
• Feature request
• Documentation issue or request (new chapter/page)
• Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current Behavior

The NestJS documentation for Websockets and rate limiting provides an example of using the throttler guard with Websockets. However, it does not take into account multiple throttle limit configurations. The handleRequest method will be called multiple times when multiple throttler limits are set.

Expected Behavior

The documentation should be updated to reflect that users need to handle multiple throttle limits if they are configured, rather than just a single limit. This ensures users are not misled into writing code that only handles one limit, which is no longer valid with multiple throttler limits configured.

[kamilmysliwiec]

PRs are more than welcome if you're interested to contribute!