[REFACTOR/#118] AWS S3 SDK v2 마이그레이션 및 분리되어 있던 테이블 통합

[ckkim817]

💡 Issue

• resolved: [REFACTOR] AWS S3 SDK v2 마이그레이션 및 분리되어 있던 테이블 통합 #118

📄 Description

• AWS S3 SDK v2 마이그레이션에 따른 Presigned URL 획득 로직 수정
• Presigned URL 획득 과정에 이미지 파일 확장자를 검증하는 로직 추가
• apply_spot 테이블에서 관리하던 신청 장소 데이터들을 spot 테이블로 통합
• spot 데이터 삽입 전까지 임시 s3 경로에 저장하던 이미지들을 정상 경로로 이동시키는 로직 추가
• 누락되어 있던 Member 탈퇴 시 연관 엔티티 cascade delete 처리 로직 추가

[Copilot]

Pull Request Overview

This PR migrates the application to AWS S3 SDK v2 and consolidates the spot application data management by integrating previously separated tables. The major changes include updating the S3 adapter for presigned URL generation with file validation, consolidating apply_spot data into the main spot table, and adding cascade delete functionality for member withdrawal.

• AWS S3 SDK v2 migration with enhanced file validation and presigned URL generation
• Table consolidation: moving apply_spot data directly into spot table with status tracking
• Member withdrawal cascade delete implementation for related entities

Reviewed Changes

Copilot reviewed 23 out of 24 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
S3Adapter.java	Complete migration to AWS SDK v2 with file validation and move operations
SpotService.java	Refactored spot application logic to use main spot table instead of separate apply_spot table
SpotEntity.java	Added appliedMemberId and spotStatus fields to support consolidated data model
MemberService.java	Updated presigned URL generation with file extension validation and cascade delete logic
ImageType.java	Enhanced with file extension validation and content type mapping
SpotStatus.java	New enum to track spot application status

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Consider using EnumMap instead of HashMap for better performance and type safety when mapping enum values.

[Copilot]

Validating images individually in a loop can be inefficient for large image lists. Consider batch validation or parallel processing for better performance.

Suggested change

	for (String imageUrl : request.imageList()) {
	s3Adapter.validateImageExists(imageUrl);
	}
	request.imageList().parallelStream().forEach(s3Adapter::validateImageExists);

[Copilot]

Moving files sequentially in a loop can be slow for multiple images. Consider using parallel processing or batch operations for S3 file moves.

Suggested change

	for (String imageUrl : request.imageList()) {
	String fileName = imageUrl.substring(imageUrl.lastIndexOf("/") + 1);
	String destinationKey = String.format("spots/%d/spot/%s", spotId, fileName);
	String newImageUrl = s3Adapter.moveFile(imageUrl, destinationKey);
	movedImageList.add(newImageUrl);
	}
	movedImageList.addAll(
	request.imageList().parallelStream()
	.map(imageUrl -> {
	String fileName = imageUrl.substring(imageUrl.lastIndexOf("/") + 1);
	String destinationKey = String.format("spots/%d/spot/%s", spotId, fileName);
	return s3Adapter.moveFile(imageUrl, destinationKey);
	})
	.collect(Collectors.toList())
	);

[Copilot]

Consider using EnumMap instead of HashMap for better performance and type safety when mapping enum values.

[Copilot]

Sequential deletion operations can be inefficient. Consider using @transactional with batch operations or database cascade delete constraints for better performance.

Suggested change

	preferenceRepository.deleteById(memberId);
	guidedSpotRepository.deleteAllByMemberId(memberId);
	savedSpotRepository.deleteAllByMemberId(memberId);
	verifiedAreaRepository.deleteAllByMemberId(memberId);
	// Related entities are deleted via cascade delete from MemberEntity.