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.

Inizia individuando le definizioni delle route API e gli endpoint supportati da Celery, quindi fai un inventario delle operazioni a cui deve essere applicato ciascun limite di frequenza. Chiarisci le soglie al minuto e il meccanismo di limitazione della frequenza prima dell’implementazione. Il lavoro è completato quando le richieste sono limitate in modo diverso per gli endpoint Celery e non-Celery, impedendo il sovraccarico della coda o delle risorse.