Include TotalSummary in CRUD responses to eliminate redundant API calls

Backend changes:
- Add WithSummaryResponse wrappers for Task, TaskCompletion, and Residence CRUD
- Update services to return summary with all mutations (create, update, delete)
- Update handlers to pass through new response types
- Add getSummaryForUser helper for fetching summary in CRUD operations
- Wire ResidenceService into TaskService for summary access
- Add summary field to JoinResidenceResponse

This optimization eliminates the need for a separate getSummary() call after
every task/residence mutation, reducing network calls from 2 to 1.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

internal/dto/responses/residence.go

@@ -69,6 +69,18 @@ type MyResidencesResponse struct {
 	Summary    TotalSummary        `json:"summary"`
 }
 
+// ResidenceWithSummaryResponse wraps ResidenceResponse with TotalSummary for CRUD operations
+type ResidenceWithSummaryResponse struct {
+	Data    ResidenceResponse `json:"data"`
+	Summary TotalSummary      `json:"summary"`
+}
+
+// ResidenceDeleteWithSummaryResponse for delete operations
+type ResidenceDeleteWithSummaryResponse struct {
+	Data    string       `json:"data"`
+	Summary TotalSummary `json:"summary"`
+}
+
 // ShareCodeResponse represents a share code in the API response
 type ShareCodeResponse struct {
 	ID          uint       `json:"id"`
@@ -84,6 +96,7 @@ type ShareCodeResponse struct {
 type JoinResidenceResponse struct {
 	Message   string            `json:"message"`
 	Residence ResidenceResponse `json:"residence"`
+	Summary   TotalSummary      `json:"summary"`
 }
 
 // GenerateShareCodeResponse represents the response after generating a share code