refactor: 플레이어 init을 GET 로드 + POST 생성으로 분리

[Sean-mn]

📚작업 내용

• 플레이어 init 단일 엔드포인트를 GET /v1/player(로드)와 POST /v1/player(생성)로 분리
• GetPlayerService 추가: Redis 캐시 우선 조회, 미스 시 DB 조회 후 캐시 적재, 플레이어 미존재 시 404
• CreatePlayerService 추가: 트랜잭션으로 player/resource/stage/session 생성, 이미 존재하면 409, 생성 후 Redis 캐시 적재
• 기존 InitPlayerService/IInitPlayerService/InitPlayerRequest 제거 → CreatePlayerRequest, IGetPlayerService/ICreatePlayerService로 대체
• PlayerServiceConfig DI 등록을 신규 서비스에 맞게 갱신
• Production Swagger Basic Auth 보호(SwaggerBasicAuthMiddleware) 및 관련 Program.cs/compose.prod.yaml 설정 제거
• 클라이언트 연동 가이드 문서 추가 및 GET 로드 + POST 생성 흐름으로 갱신, 골드/티켓 충전 표현 명확화

◀️참고 사항

• API 계약 변경: POST /v1/player/init → GET /v1/player + POST /v1/player. 클라이언트는 로드(GET) 후 404면 생성(POST)하는 흐름으로 동작
• 테스트: GetPlayerServiceTest, CreatePlayerServiceTest 신규 추가, 기존 InitPlayerServiceTests 제거, 라우트 테스트를 GET/POST 구조로 갱신
• 본 PR은 기존 Swagger/문서 PR(update: Production Swagger 공개 전환 및 클라이언트 연동 가이드 추가 #28)을 대체합니다

✅체크리스트

[ ]안에 x를 작성하면 체크박스를 체크할 수 있습니다.

• 현재 의도하고자 하는 기능이 정상적으로 작동하나요?
• 변경한 기능이 다른 기능을 깨뜨리지 않나요?

추후 필요한 체크리스트는 업데이트 될 예정입니다.

[gemini-code-assist]

Code Review

This pull request redesigns the player loading and creation flow by splitting the combined POST /v1/player/init endpoint into a GET /v1/player endpoint for loading player data and a POST /v1/player endpoint for player creation. It updates the corresponding services, controllers, DI registrations, unit tests, and client integration documentation. The review feedback highlights two important issues: first, a potential client-side deadlock if a player exists but has missing related data, where throwing a 404 instead of a 500 would cause a loop of creation failures; second, a concurrency race condition during simultaneous player creation requests that could be mitigated by handling database unique constraint violations or using locks.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Code Review

This pull request refactors the player initialization flow by splitting the combined load/create endpoint (POST /v1/player/init) into two distinct endpoints: GET /v1/player for loading player data and POST /v1/player for creating a new player. Correspondingly, InitPlayerService is split into GetPlayerService and CreatePlayerService, and the request DTO is renamed to CreatePlayerRequest. Additionally, the production Swagger basic authentication middleware is removed. Feedback on the changes suggests adding [EnumDataType(typeof(JobType))] validation to the CreatePlayerRequest to prevent invalid enum values from bypassing model validation.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.