fix: 서버 응답 구조에 맞게 DTO 수정

- maxHeartRateConfig 타입 Int → Double (서버가 190.0으로 반환)
- HealthSummaryResponseDto에 summary nested 구조 반영

Author: thingineeer

Runnect-iOS/Runnect-iOS/Network/Dto/RunningDto/RequestDto/HealthDataSaveRequestDto.swift

@@ -19,7 +19,7 @@ struct HealthDataSaveRequestDto: Codable {
     let zone3Seconds: Int
     let zone4Seconds: Int
     let zone5Seconds: Int
-    let maxHeartRateConfig: Int?
+    let maxHeartRateConfig: Double?
     let heartRateSamples: [HeartRateSampleDto]?
 }
 

Runnect-iOS/Runnect-iOS/Network/Dto/RunningDto/ResponseDto/HealthDataResponseDto.swift

@@ -23,7 +23,7 @@ struct HealthDataDetail: Codable {
     let minHeartRate: Double?
     let calories: Double
     let zones: HealthZonesDto
-    let maxHeartRateConfig: Int?
+    let maxHeartRateConfig: Double?
     let heartRateSamples: [HeartRateSampleDto]?
 }
 

Runnect-iOS/Runnect-iOS/Network/Dto/RunningDto/ResponseDto/HealthSummaryResponseDto.swift

@@ -10,6 +10,12 @@ import Foundation
 // MARK: - HealthSummaryResponseDto
 
 struct HealthSummaryResponseDto: Codable {
+    let summary: HealthSummaryDetail
+}
+
+// MARK: - HealthSummaryDetail
+
+struct HealthSummaryDetail: Codable {
     let totalRecords: Int
     let recordsWithHealth: Int
     let avgHeartRate: Double?