Feat prevent renaming habits with existing logs clone instead

[BrayanMQ]

📝 Description

Implement soft versioning for habits to prevent data integrity issues when renaming habits with existing logs. When a user attempts to rename a habit that has recorded history, instead of modifying the original habit, the system creates a new habit with the new name and archives the original one, preserving all historical data.

🔗 Related Issue

Closes #83

🏷️ Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Dependency update

🔄 Changes Made

• Added archived_at column to habits table via SQL migration
• Modified useHabits hook to filter out archived habits from the main list
• Added new hooks: useArchivedHabits and useArchiveHabit for managing archived habits
• Added useHabitHasLogs hook to check if a habit has existing logs before allowing rename
• Updated EditHabitModal to show confirmation dialog when renaming habits with logs
• Created ArchivedHabitsSection component with collapsible UI to display archived habits
• Added archived habits section to the habits management page
• Added EN/ES translations for all new UI elements

🧪 Testing

• Manual testing completed
• Unit tests added/updated
• Integration tests added/updated

Test steps:

1. Create a new habit without logs → Edit name → Should update normally
2. Create a habit and mark it as completed (creates a log) → Edit name → Should show confirmation modal
3. Confirm the action → Should create new habit and archive the original
4. Navigate to habits page → Archived section should appear at the bottom with the archived habit

✅ Checklist

• My code follows the project's code style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly (if applicable)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

📸 Screenshots (if applicable)

N/A - UI changes are minimal (collapsible archived section and confirmation modal)

📌 Additional Notes

Database Migration Required:

ALTER TABLE public.habits ADD COLUMN archived_at TIMESTAMPTZ;
CREATE INDEX IF NOT EXISTS idx_habits_archived_at ON public.habits(archived_at);

Run npx supabase db push to apply the migration before testing.

Files Changed:

• supabase/migrations/20260113100000_add_habits_archived_at.sql (new)
• types/database.ts
• hooks/useHabits.ts
• hooks/useHabitLogs.ts
• components/habits/EditHabitModal.tsx
• components/habits/ArchivedHabitsSection.tsx (new)
• app/dashboard/habits/page.tsx
• i18n/locales/en.json
• i18n/locales/es.json
• Test files updated with archived_at property