Limiting Abuse Control (rate-limiting) to Client-Side Integrations

I'm thinking of limiting the abuse checks to client-side integrations only for all Appwrite different endpoints. I think it's becoming a bit limiting and counterproductive when using Appwrite with an API key.

We use rate-limiting today for mainly two scenarios. The first one is the protection of user authentication, and the second one is protecting write-heavy operations. Both cases are much more dangerous when we're talking about end-users access rather than just an internal server integration using an API key or upcoming JWT authentication methods.

I would love to get more community and team feedback about this before making any changes in the code.