#138 - 쪽지 답장을 사용한적이 있는지 확인하는 API를 구현합니다.

[kpeel5839]

1. 🔗 관련 이슈

closes #138

2. 📄 구현한 내용 또는 수정한 내용

• 쪽지 답장을 사용한적이 있는지 확인하는 API를 구현했습니다.

3. ✅ 배포 Checklist

• 본인을 Assign 해주세요.
• 본인을 제외한 백엔드 개발자를 리뷰어로 지정해주세요.
• 변경된 DB 업데이트 해주세요. (꼭 해주세요 배포 안돼요!!!)

[Copilot]

Pull Request Overview

This PR implements an API endpoint to check whether a user has previously used the answer message feature.

• Adds a new repository method to retrieve answer message usage by user ID.
• Implements a persistence adapter and service method for domain mapping.
• Introduces a REST controller to expose the feature status via a GET endpoint.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
infrastructure/mysql/src/main/kotlin/com/wespot/user/repository/UsedAnswerMessageJpaRepository.kt	Added repository method findByUserId to support domain lookup.
infrastructure/mysql/src/main/kotlin/com/wespot/user/adapter/UsedAnswerMessagePersistenceAdapter.kt	Mapped the repository entity to the domain model via a new method.
core/src/main/kotlin/com/wespot/user/service/UsedAnswerMessageService.kt	Created a service that retrieves the feature status for a user.
core/src/main/kotlin/com/wespot/user/port/in/UsedAnswerMessageUseCase.kt	Defined a new use case interface for the feature check.
app/src/main/kotlin/com/wespot/user/UsedAnswerMessageController.kt	Added a controller exposing the API endpoint for the feature check.

[Copilot]

[nitpick] The endpoint path '/api/v2/messages/answer/first' does not clearly indicate that it checks for the usage of the answer message feature. Consider renaming the path to something more descriptive, such as '/api/v2/messages/answer/feature-status', to better convey its purpose.

Suggested change

	@RequestMapping("/api/v2/messages/answer/first")
	@RequestMapping("/api/v2/messages/answer/feature-status")

[kpeel5839]

No Thanks