Description:
This feature request is follow up from Slack discussion with @arkodg .

The functionality for defining multiple rate limits was previously available through RateLimitFilters. However, these filters were removed from the codebase around version 0.6.0. A new CRD named BackendTrafficPolicy was introduced, and the rateLimit field now belongs to this CRD.

It would be beneficial to be able to define multiple rate limits again for entire paths within BackendTrafficPolicy. This would allow for a use case where a "basic" rate limit could be applied to unauthenticated clients, while a stricter "proper" rate limit could be applied to users with valid JWT authentication (basic authentication is a separate consideration).