Implement ratelimits

[No767]

Summary

This PR aims to implement an robust ratelimiting system. This is done now so we can focus on building the actual API next. Although this ratelimiter implementation does use slowapi, I think it will be fine for now. The only other library basically doesn't even work at all from the last time I checked. Although this library does block the event loop, hopefully it shouldn't accept the performance of the app.

In addition, Redis is used here to synchronize the ratelimit cache. We could always use Redis to build an cache later on.

Types of changes

What types of changes does your code introduce to Kanae?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes. (if appropriate)
• All workflows (except pre-commit.ci) pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud