feat(libs): Add API key rate limit middleware

[aarushik93]

Once we release api key feature, we will want to be able to rate limit as well. This is the foundation for that.
For now it is a blanket rate limit, later we will be able to add tiered rate limits

Changes 🏗️

Added new middleware libary in autogpt_libs which contains the logic for getting the api key, storing it's details in redis and checking how many requests it's done, how many are left and what the reset time is.

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	f36be90
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/674ece36a5b8510008303b4d

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	f36be90
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/674ece363c7a9300083f987d

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 Security concerns Redis Security: The default Redis configuration uses localhost without authentication or TLS. In production, this could expose the rate limiting data if Redis is accessible externally. Should enforce secure Redis connection configuration with authentication and TLS.

⚡ Recommended focus areas for review Security Issue The middleware accepts any API key format and doesn't validate the key format or authenticity before rate limiting. Should verify API key is valid before applying rate limits. Race Condition The Redis operations are not atomic which could lead to race conditions under high concurrency. Consider using Redis MULTI/EXEC or Lua scripting. Configuration Risk Default Redis URL uses localhost without authentication, which could be a security risk if accidentally used in production.