Rewrite logic of habit status computation

[DanielRendox]

refactor routine to habit;
use HabitStatus instead of HistoricalStatus and PlanningStatus; add additional statuses for clarity;
rewrite logic of habit status computation so that both: historical and future statuses can be computed on the go instead of being cashed in the database, the only data that needs to be stored is the number of times completed;

[github-actions]

PR Analysis

• 🎯 Main theme: Rewrite logic of habit status computation
• 📝 PR summary: Refactor routine to habit; use HabitStatus instead of HistoricalStatus and PlanningStatus; add additional statuses for clarity; rewrite logic of habit status computation so that both historical and future statuses can be computed on the go instead of being cached in the database, the only data that needs to be stored is the number of times completed.
• 📌 Type of PR: Enhancement
• 🧪 Relevant tests added: False
• ⏱️ Estimated effort to review [1-5]: 3, because the PR introduces changes to multiple files and involves logic changes in the code.
• 🔒 Security concerns: No security concerns found

PR Feedback

• 💡 General suggestions:

  • The PR description could be more detailed, providing more context about the changes made and the motivation behind them.
  • Consider adding relevant tests to cover the new logic introduced in the code.
  • Make sure to update the commit messages to be more descriptive and concise.
• 🤖 Code feedback:

  ---

  relevant file	core/domain/src/main/java/com/rendox/routinetracker/core/domain/completion_history/use_cases/ToggleHistoricalStatusUseCase.kt
  suggestion	Consider renaming the class `ToggleHistoricalStatusUseCase` to `ToggleHabitStatusUseCase` to reflect the change from `Routine` to `Habit`.
  relevant line	class ToggleHistoricalStatusUseCase(

  ---

  relevant file	core/domain/src/main/java/com/rendox/routinetracker/core/domain/completion_history/HabitComputeStatusUseCase.kt
  suggestion	Consider renaming the class `HabitComputeStatusUseCase` to `ComputeHabitStatusUseCase` to follow a more consistent naming convention.
  relevant line	class HabitComputeStatusUseCase(

  ---

  relevant file	core/domain/src/main/java/com/rendox/routinetracker/core/domain/completion_history/use_cases/InsertRoutineStatusUseCase.kt
  suggestion	Consider renaming the class `InsertRoutineStatusUseCase` to `InsertHabitStatusUseCase` to reflect the change from `Routine` to `Habit`.
  relevant line	class InsertRoutineStatusUseCase(

  ---

  relevant file	core/domain/src/main/java/com/rendox/routinetracker/core/domain/completion_history/use_cases/GetRoutineStatusUseCase.kt
  suggestion	Consider renaming the class `GetRoutineStatusUseCase` to `GetHabitStatusUseCase` to reflect the change from `Routine` to `Habit`.
  relevant line	class GetRoutineStatusUseCase(

  ---

How to use

Instructions

To invoke the PR-Agent, add a comment using one of the following commands:
/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs: Generate docstring for new components introduced in the PR.
/generate_labels: Generate labels for the PR based on the PR's contents.
see the tools guide for more details.

To edit any configuration parameter from the configuration.toml, add --config_path=new_value.
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, add a /config comment.

[DanielRendox]

@CodiumAI-Agent /review