fix: file creation validation and error handling in DefaultCreateFile…

[jhonatapers]

This pull request enhances file creation functionality by improving validation and exception handling in the DefaultCreateFileUseCase class and updating its corresponding test suite. Key changes include stricter validation for file names, enhanced quota checks, and additional test cases to cover new scenarios.

Enhancements to validation and exception handling:

• Introduced validation for file names to ensure they are not reserved or duplicate within the same folder. Added a Notification object to collect validation errors, and a ValidationException is thrown if errors are present. (DefaultCreateFileUseCase.java, [1] [2]
• Updated quota check logic to use the Error.with method for consistency when throwing QuotaExceededException. (DefaultCreateFileUseCase.java, application/src/main/java/com/callv2/drive/application/file/create/DefaultCreateFileUseCase.javaL62-R79)

Test suite improvements:

• Added test cases to validate new scenarios, including:
  • Invalid member ID leading to a NotFoundException.
  • Invalid file names (e.g., reserved names like "NUL") causing a ValidationException.
  • Quota exceeded scenarios resulting in a QuotaExceededException.
  • Null content type causing a ValidationException.
• Renamed test methods for clarity, such as changing givenAnInvalidId_whenCallsExecute_thenShouldThrowNotFoundException to givenAnInvalidFolderId_whenCallsExecute_thenShouldThrowNotFoundException.

Code cleanup:

• Removed redundant logic for file name validation and notification handling in the DefaultCreateFileUseCase class, as these are now handled earlier in the process. (DefaultCreateFileUseCase.java, application/src/main/java/com/callv2/drive/application/file/create/DefaultCreateFileUseCase.javaL78-L84)
• Adjusted test verifications to align with updated validation logic, ensuring no unnecessary operations (e.g., file storage) are performed when validation fails. [1] [2]