Feature/quota summary

[jhonatapers]

This pull request introduces a new feature to provide an aggregated summary of quota usage and allocation for members, along with several supporting changes and some minor naming corrections. The main focus is on implementing the quota summary use case, exposing it via the API, and updating the data access and domain layers to support the required statistics.

Quota summary feature:

• Added the GetQuotasSummaryUseCase abstract class and its implementation DefaultGetQuotasSummaryUseCase, which aggregates total members, total allocated quota, total used storage, and total available quota. (application/src/main/java/com/callv2/drive/application/member/quota/retrieve/summary/GetQuotasSummaryUseCase.java [1] DefaultGetQuotasSummaryUseCase.java [2]
• Introduced the output DTO GetQuotasSummaryOutput to encapsulate the summary data. (GetQuotasSummaryOutput.java application/src/main/java/com/callv2/drive/application/member/quota/retrieve/summary/GetQuotasSummaryOutput.javaR1-R9)
• Added the API endpoint /admin/members/quotas/summary to MemberAdminAPI and implemented it in MemberAdminController, returning a QuotaSummaryResponse. (MemberAdminAPI.java [1] [2]; QuotaSummaryResponse.java [3]
• Registered the new use case bean in the configuration. (MemberUseCaseConfig.java infrastructure/src/main/java/com/callv2/drive/infrastructure/configuration/usecase/MemberUseCaseConfig.javaR64-R68)

Domain and persistence support for quota statistics:

• Added count() and sumAllQuota() methods to MemberGateway and implemented them in DefaultMemberGateway and MemberJpaRepository. (MemberGateway.java [1] [2]; DefaultMemberGateway.java [3] [4]
• Added sumAllContentSize() to FileGateway and implemented it in FileJPAGateway and FileJpaRepository. (FileGateway.java [1] FileJPAGateway.java [2] FileJpaRepository.java [3]

API and naming consistency improvements:

• Corrected the spelling of "ammount" to "amount" in DTOs, API descriptions, and entity fields for clarity and consistency. (CreateRequestQuotaInput.java [1] DefaultCreateRequestQuotaUseCase.java [2] MemberAPI.java [3] MemberAdminAPI.java [4]
• Updated MemberJpaEntity and related code to use quotaAmount, quotaInBytes, and similar consistent field names. (MemberJpaEntity.java [1] [2] DefaultMemberGateway.java [3]

These changes collectively enable administrators to retrieve an overview of quota allocation and usage, and improve overall code clarity and maintainability.