Release v0.3.0

[jhonatapers]

This pull request introduces a new feature to provide an aggregated summary of drive quotas, including total allocated, used, and available quotas, as well as the total number of members. It also includes several supporting changes such as new use case classes, API endpoints, and gateway methods, as well as some minor corrections to naming and documentation.

New Quota Summary Feature

• Added GetQuotasSummaryUseCase, its default implementation, and output record to aggregate and return a summary of quotas across all members (GetQuotasSummaryUseCase, DefaultGetQuotasSummaryUseCase, GetQuotasSummaryOutput). [1] [2] [3]
• Exposed a new admin API endpoint GET admin/members/quotas/summary to retrieve the quota summary, with corresponding controller and response model (MemberAdminAPI, MemberAdminController, QuotaSummaryResponse). [1] [2] [3]

Gateway and Repository Enhancements

• Added methods to MemberGateway and FileGateway to support counting members and summing quotas/content sizes, with implementations in the infrastructure layer and JPA repositories. [1] [2] [3] [4] [5] [6] [7]

Configuration Updates

• Registered the new use case in the Spring configuration so it can be injected where needed (MemberUseCaseConfig). [1] [2]

Naming Corrections and Consistency

• Fixed typos in parameter and variable names from ammount to amount throughout the application, including API documentation, DTOs, and persistence entities. [1] [2] [3] [4] [5] [6] [7]

API Documentation Improvements

• Updated API operation descriptions to use the correct spelling "amount" instead of "ammount" for clarity and professionalism. [1] [2]

Let me know if you'd like to walk through any part of the new quota summary logic or have questions about the new gateway methods!