Security: Introduce rate limit per endpoint

Describe the current behavior
Currently, Kaapi API endpoints have no rate limiting implemented. Any user or organization can make unlimited requests to any endpoint without restrictions. This creates several issues:

• A single user or organization can overwhelm the API with requests, consuming server resources and degrading performance for other users
• There's no protection against accidental or malicious misuse, such as runaway scripts or bot activity
• Celery operations like document uploads with provider integration or collection creation can cause celery job queue bloating

Describe the enhancement you'd like
Implement api level rate limiting across relevant API routes to ensure fair resource allocation and prevent misuse. The rate limiting should be conditional based on if it is a celery job endpoint or not. celery job endpoints such as collection creation, llm calls, etc should have lower number of api calls allowed per minute as compared to non celery job endpoints such as credential, onboarding, etc which can have higher number of api calls allowed per minute.

Commencez par localiser les définitions des routes API et les endpoints pris en charge par Celery, puis dressez l’inventaire des opérations qui doivent recevoir chaque limite de débit. Clarifiez les seuils par minute et le mécanisme de limitation du débit avant l’implémentation. Le travail est considéré comme terminé lorsque les requêtes sont limitées différemment pour les endpoints avec et sans Celery, afin d’éviter la surcharge de la file d’attente ou des ressources.