Consolidate task mutation completion handling

[coderabbitai]

Summary

Extract the repeated task mutation completion sequence into useTaskMutation(document, messages).

Required changes

• Centralize query invalidation, notification, and dialog close behavior.
• Replace duplicated mutation completion logic in each task mutation UI.

Affected areas

• CreateTaskModal
• EditTaskModal
• DeleteTaskDialog
• New useTaskMutation hook

Acceptance criteria

• The three task mutation flows use the shared hook.
• Invalidate, notify, and close behavior remains unchanged.

Source

• Review comment: docs(readme): improve instructions #42 (comment)
• Pull request: docs(readme): improve instructions #42
• Requested by: @Alejandroq12

[coderabbitai]

Technical note

Extract the shared mutation lifecycle, not the task-specific inputs. The hook should accept the mutation document and explicit success/error messages. Preserve operation-specific variables and callbacks. Define the order of success effects, such as invalidate, notify, then close, and test that each caller keeps its current behavior.

Reference: React: Reusing logic with custom Hooks

[coderabbitai]

Engineering note

Extract the repeated workflow only when its inputs and outputs are explicit. The hook should own mutation completion effects, while each dialog keeps its mutation-specific variables and UI. Keep error behavior and success-message differences configurable, then test all three callers.

Read: React: Reusing logic with custom Hooks