🔆 Add Cascading deletes on the repo and add Rate limiting to API

[nahomderese]

Description

To enhance the robustness and scalability of our application, we need to implement two critical features: cascading deletes in the repository and rate limiting for the API.

Objectives:

Cascading Deletes:

Implement cascading delete functionality across the repository to ensure that when a primary entity is deleted, all related entities are automatically deleted as well. This will prevent orphaned records and maintain data integrity.

Rate Limiting:

Introduce rate limiting to the API to protect against abuse and ensure fair usage of resources. This will involve setting limits on the number of requests that can be made within a specific time frame, thereby preventing potential denial-of-service attacks and improving overall API performance.

Expected Outcome:

Cascading Deletes:

All associated data will be consistently and automatically cleaned up when a parent entity is removed, reducing the risk of data inconsistencies.

Rate Limiting:

The API will be more resilient to high traffic and potential misuse, providing a more reliable and stable service to all users.